Skip to content
Snippets Groups Projects
Commit a2af6bbe authored by Georges Racinet's avatar Georges Racinet
Browse files

Gitaly Comparision tests: checking for rich errors

As explained in #108, Gitaly now can provide rich errors as
response "trailing metadata".

We don't implement these, but we can already check that we don't
miss any. Since the test passes, it means that all that would
be relevant to the subset of protocol that we implement are
still behind feature flags that don't default to `true`.
parent ab7ef938
No related branches found
No related tags found
No related merge requests found
Pipeline #62644 failed
......@@ -240,6 +240,11 @@
if same_details:
assert exc_hg.details() == exc_git.details()
# trailing metadata can bear a typed error gRPC message, which
# is more important to compare than "details" (in the sense of
# human-readable message), so let's check them unconditionally:
assert exc_hg.trailing_metadata() == exc_git.trailing_metadata()
return exc_hg, exc_git
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment