This is an archive of the discontinued Mercurial Phabricator instance.

errors: use detailed exit code 50 for StorageError
ClosedPublic

Authored by martinvonz on Dec 14 2020, 4:31 PM.

Diff Detail

Repository
rHG Mercurial
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

martinvonz created this revision.Dec 14 2020, 4:31 PM

Many of the LFS errors feel weird too, because they are explicitly mentioning the remote server. I didn't check, but I suspect that this is because it's being raised in the filelog wrapper, so a remote error isn't appropriate? The wiki page talked about IOError and file corruption, so I probably went into this with too narrow of a view on the storage layer. I'm not worried about it, but I thought I'd point it out.

tests/test-committer.t
105

Weird, this seems like it's a config or input error. But since it was already like this and just changing the exit code, I'll keep going and queue it. (There are a couple more instances of this in test-mq-qrefresh.t.)

mharbison72 accepted this revision.Dec 15 2020, 10:59 PM
This revision is now accepted and ready to land.Dec 15 2020, 10:59 PM
This revision was automatically updated to reflect the committed changes.
mharbison72 added inline comments.Jan 16 2021, 8:30 PM
tests/test-lfs-test-server.t
463

Any thoughts on why this is exiting with 255 on Windows, but not elsewhere? (It appears to be a py3 only failure)

martinvonz added inline comments.Jan 17 2021, 1:56 AM
tests/test-lfs-test-server.t
463

Maybe line 37 in this file? Does it happen only in the #git-server case? I barely know anything about LFS, so maybe my guess is completely off (I don't know what that spawn.py scripts is about). I don't have access to a Windows machine, so do you think you can fix it?