CodeOwnerConfigValidatorIT: Fix flaky tests

If an import in a code owner config cannot be resolved the error message
always contains the revision in which the code owner config was not
found. If the import is done from another project this is the revision
of the other project.

The tests that were added in change Iadbe4262d wrongly expected to see
parent1 of the merge commit in the error message. This was only working
since the test framework by chance created the same initial commit in
both projects (same SHA1). If the creation of the initial commits are
not done in the same second the SHA1 differs and the tests fails.

Fix the bad assertions in the tests.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Ifb54d0d6f1d4d46c66dcbe94a479fe6e5579cf19
1 file changed
tree: 05469e50c1844f4a20a6cb9fd92634f1dfce2f08
  1. java/
  2. javatests/
  3. proto/
  4. resources/
  5. test/
  6. ui/
  7. .eslintrc.json
  8. .gitignore
  9. .gitreview
  10. bower.json
  11. BUILD
  12. LICENSE
  13. package-lock.json
  14. package.json
  15. README.md
README.md

Gerrit Code Review code-owners plugin

This plugin provides support for defining code owners for files in a repository.

If the code-owners plugin is enabled, changes can only be submitted if all touched files are covered by approvals from code owners.

Also see resources/Documentation/about.md.

IMPORTANT: Before installing/enabling the plugin follow the instructions from the setup guide, see resources/Documentation/setup-guide.md.