-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
recordstatus gives different values for errors on windows and github #383
Comments
I guess we should perhaps coerce status 256 to be the same as 1 - that's where the issue really lies. I'm wary of doing more - what if 1 vs 2 vs ... is important? |
256 should not be a special case but we should use |
@zauguin OK, I'll assign this one to you :) |
I'm trying to use recordstatus in various testsuites (to get better warnings about unrelated errors from deprecation and similar).
It works fine for tests with status 0 (no error), but fails for non-zero status. E.g. if I save a simple test with a
\show\START
on windows and then test that on github I get the following diff:Could l3build please normalize that message to something like
with non-zero exit status
?The text was updated successfully, but these errors were encountered: