-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Always produce artifact messages #3752
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
That's the minimal work needed for #3670 I think. |
Looks good to me! Could this perhaps also include a json key to indicate whether the artifact was just compiled or not? |
☔ The latest upstream changes (presumably #3733) made this pull request unmergeable. Please resolve the merge conflicts. |
eb3adc4
to
9f22fbf
Compare
9f22fbf
to
7bfd7dc
Compare
Added a "fresh" key |
@bors: r+ |
📌 Commit 7bfd7dc has been approved by |
⌛ Testing commit 7bfd7dc with merge 338c7b7... |
💔 Test failed - status-appveyor |
@bors: retry |
Always produce artifact messages This changes `artifact` messages in several ways: * They are produced even for fresh builds * They used the path after hard linking (@jsgf talked about it in the end of #3319 (comment)) * Don't produce filenames if the compiler has not actually produced the binaries (`-Z-no-trans`).
☀️ Test successful - status-appveyor, status-travis |
This changes
artifact
messages in several ways:They are produced even for fresh builds
They used the path after hard linking (@jsgf talked about it in the end of Emit more info on --message-format=json #3319 (comment))
Don't produce filenames if the compiler has not actually produced the binaries (
-Z-no-trans
).