Mercurial > hg-stable
changeset 46339:47b11629a0f2 stable
tests: skip a detailed exit status in test-lfs-test-server
The mode of failure here differs between `lfs-test-server` and `hg serve`, and
they each throw a different exception. The `hg serve` case raises a subclass of
`StorageError`, which gets a detailed status. The `lfs-test-server` case raises
a subclass of `Abort`, which does not. Since the exit code isn't currently
conditionizable in the tests, this is the simplest way to avoid the failure.
Differential Revision: https://phab.mercurial-scm.org/D9836
| author | Matt Harbison <matt_harbison@yahoo.com> |
|---|---|
| date | Wed, 20 Jan 2021 00:40:41 -0500 |
| parents | c4787ea85cc7 |
| children | 6bb52cc08855 |
| files | tests/test-lfs-test-server.t |
| diffstat | 1 files changed, 5 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/tests/test-lfs-test-server.t Wed Jan 20 14:57:56 2021 +0100 +++ b/tests/test-lfs-test-server.t Wed Jan 20 00:40:41 2021 -0500 @@ -420,7 +420,10 @@ TODO: give the proper error indication from `hg serve` - $ hg --repo ../repo1 update -C tip --debug +TODO: reconsider the except base class so that the git and hg errors yield the +same exit status. + + $ hg --repo ../repo1 update -C tip --debug --config ui.detailed-exit-code=False http auth: user foo, password *** resolving manifests branchmerge: False, force: True, partial: False @@ -460,7 +463,7 @@ Date: $HTTP_DATE$ (git-server !) abort: corrupt remote lfs object: d11e1a642b60813aee592094109b406089b8dff4cb157157f753418ec7857998 (git-server !) abort: LFS server error for "c": Validation error (hg-server !) - [50] + [255] The corrupted blob is not added to the usercache or local store