-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Better diagnostics for dlltool errors. #112591
Conversation
r? @fee1-dead (rustbot has picked a reviewer for you, use r? to override) |
Example of output:
(Note that the underlying problem causing this particular error is that llvm-dlltool doesn't support --temp-prefix, which I intend to address separately.) |
This comment has been minimized.
This comment has been minimized.
I'm not familiar with this. r? compiler |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you squash the commits together?
4ca05d1
to
4bdba91
Compare
Squashed. Thanks for the review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@bors r+ rollup |
… r=WaffleLapkin Better diagnostics for dlltool errors. When dlltool fails, show the full command that was executed. In particular, llvm-dlltool is not very helpful, printing a generic usage message rather than what actually went wrong, so stdout and stderr aren't of much use when troubleshooting.
@bors r- failed in rollup: #112851 (comment) |
@jfgoog you need to find a way to bless the test in such a way, it passes both in CI and locally (this might be non-trivial, given that the test includes paths...) |
4bdba91
to
d1f68ea
Compare
Done. I'm not able to test locally, since I'm building on Linux and using llvm-dlltool, which produces different output, which is the entire reason for this change. Is there a way to trigger the build that failed without sending to submit queue? |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
This looks like a legitimate failure, probably needs some blessing. |
I've been on vacation. Will take a look soon. |
When dlltool fails, show the full command that was executed. In particular, llvm-dlltool is not very helpful, printing a generic usage message rather than what actually went wrong, so stdout and stderr aren't of much use when troubleshooting.
d1f68ea
to
c59b823
Compare
OK, I think it's fixed, but I unfortunately don't have a good way to test locally, as I mentioned previously. |
@bors r+ Let's try it |
⌛ Testing commit c59b823 with merge 75bcdc515f778584d42b0050cc105ab12d5a0c98... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry crates.io error |
☀️ Test successful - checks-actions |
Finished benchmarking commit (77e24f9): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 647.114s -> 647.294s (0.03%) |
When dlltool fails, show the full command that was executed. In particular, llvm-dlltool is not very helpful, printing a generic usage message rather than what actually went wrong, so stdout and stderr aren't of much use when troubleshooting.