Skip to content
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

os/signal: TestCtrlBreak fails with "exit status 0xc000013a" error #29744

Open
alexbrainman opened this issue Jan 15, 2019 · 2 comments
Open

os/signal: TestCtrlBreak fails with "exit status 0xc000013a" error #29744

alexbrainman opened this issue Jan 15, 2019 · 2 comments
Labels
NeedsInvestigation OS-Windows Testing
Milestone

Comments

@alexbrainman
Copy link
Member

@alexbrainman alexbrainman commented Jan 15, 2019

Our windows-arm builder occasionally fails

https://build.golang.org/log/e345b763b3b62e4efd13bdfd95361fbc6655c3dd

with

--- FAIL: TestCtrlBreak (14.29s)
    signal_windows_test.go:102: Program exited with error: exit status -1073741510
FAIL
FAIL	os/signal	25.339s

I do not have windows-arm computer to investigate, so @jordanrh1 please investigate.

Strangely there is no output from the child process - only failed exit code.

Also the exit code is -1073741510 = 0xFFFFFFFFC000013A. Maybe C000013A have some meaning - my Google foo failed me.

Thank you

Alex

@bcmills bcmills added OS-Windows NeedsInvestigation labels Jan 29, 2019
@bcmills bcmills added this to the Go1.12 milestone Jan 29, 2019
@bcmills bcmills added the Testing label Jan 29, 2019
@andybons andybons removed this from the Go1.12 milestone Feb 12, 2019
@andybons andybons added this to the Go1.13 milestone Feb 12, 2019
@andybons andybons removed this from the Go1.13 milestone Jul 8, 2019
@andybons andybons added this to the Go1.14 milestone Jul 8, 2019
@rsc rsc removed this from the Go1.14 milestone Oct 9, 2019
@rsc rsc added this to the Backlog milestone Oct 9, 2019
@iwdgo
Copy link
Contributor

@iwdgo iwdgo commented Sep 17, 2021

0xC000013A is the exit value STATUS_CONTROL_C_EXIT. NTSTATUS says:

{Application Exit by CTRL+C} The application terminated as a result of a CTRL+C.

It might also occur on windows/amd64. On a recent tip.

--- FAIL: TestCtrlBreak (11.37s)
    signal_windows_test.go:97: Program exited with error: exit status 0xc000013a
FAIL
FAIL    os/signal       11.569s

It seems that the return code is not always received by the emitter of the Ctrl-C.
When received, it might appear as an error when it is reporting success.

The exit code is available in zerrors_windows.go. It does not seem in use anywhere else.

@alexbrainman alexbrainman changed the title os/signal: TestCtrlBreak fails on windows-arm builder os/signal: TestCtrlBreak fails with "exit status 0xc000013a" error Sep 19, 2021
@alexbrainman
Copy link
Member Author

@alexbrainman alexbrainman commented Sep 19, 2021

It might also occur on windows/amd64. On a recent tip.

Thanks for commenting here. I have adjusted issue subject accordingly.

It seems that the return code is not always received by the emitter of the Ctrl-C.
When received, it might appear as an error when it is reporting success.

I don't understand what you are trying to say here. Please try again.

Thank you.

Unrelated to your comment, but this issue is related to #46354.

Alex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation OS-Windows Testing
Projects
None yet
Development

No branches or pull requests

5 participants