We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
CL 125443 added TestExitCode. However, this test is failing on Plan 9, because Plan 9 programs return a string and not an exit code.
--- FAIL: TestExitCode (0.05s) exec_test.go:178: ExitCode got 1, want 42 exec_test.go:186: ExitCode got 1, want 2 exec_test.go:194: ExitCode got 1, want 255 FAIL FAIL os/exec 1.426s
See https://build.golang.org/log/8411cb50158709f843f78d9c6634bf005b6dc1fb
The text was updated successfully, but these errors were encountered:
It should just accept those results on Plan 9. It doesn't seem worth it to parse the int out. Even then, exit "0" would be a special case.
exit "0"
Sorry, something went wrong.
Change https://golang.org/cl/131855 mentions this issue: os/exec: pass ExitCode tests on Plan 9
os/exec: pass ExitCode tests on Plan 9
2e23475
No branches or pull requests
CL 125443 added TestExitCode. However, this test is failing on Plan 9, because Plan 9 programs return a string and not an exit code.
See https://build.golang.org/log/8411cb50158709f843f78d9c6634bf005b6dc1fb
The text was updated successfully, but these errors were encountered: