This is done as part of
https://www.mercurial-scm.org/wiki/ErrorCategoriesPlan.
Details
- Reviewers
mharbison72 - Group Reviewers
hg-reviewers - Commits
- rHG17a695357270: errors: use detailed exit code 50 for StorageError
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
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.) |
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) |
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? |
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.)