-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Spurious gdb failed to execute
on Windows
#42693
Labels
A-CI
Area: Our Github Actions CI
A-spurious
Area: Spurious failures in builds (spuriously == for no apparent reason)
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
O-windows-gnu
Toolchain: GNU, Operating system: Windows
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
Comments
This was referenced Jun 26, 2017
frewsxcv
added a commit
to frewsxcv/rust
that referenced
this issue
Jun 27, 2017
…Simulacrum compiletest: show details why GDB failed to execute. Help finding reasons of spurious errors due to GDB failing to run (rust-lang#42693).
The error code from #44261 is |
Triage: this is not actionable and hasn't been back linked to for a good while, and the failures are overly generic. Probably prefer to open more specific issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-CI
Area: Our Github Actions CI
A-spurious
Area: Spurious failures in builds (spuriously == for no apparent reason)
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
O-windows-gnu
Toolchain: GNU, Operating system: Windows
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
First seen in #41840 - https://ci.appveyor.com/project/rust-lang/rust/build/1.0.3595/job/4s8ofgv42um1t8b2:
The text was updated successfully, but these errors were encountered: