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

Always produce artifact messages #3752

Merged
merged 1 commit into from
Feb 27, 2017
Merged

Conversation

matklad
Copy link
Member

@matklad matklad commented Feb 22, 2017

This changes artifact messages in several ways:

@rust-highfive
Copy link

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

@matklad matklad changed the title Always artifacts Always produce artifact messages Feb 22, 2017
@matklad
Copy link
Member Author

matklad commented Feb 22, 2017

That's the minimal work needed for #3670 I think.

@alexcrichton
Copy link
Member

Looks good to me! Could this perhaps also include a json key to indicate whether the artifact was just compiled or not?

@bors
Copy link
Contributor

bors commented Feb 22, 2017

☔ The latest upstream changes (presumably #3733) made this pull request unmergeable. Please resolve the merge conflicts.

@matklad
Copy link
Member Author

matklad commented Feb 25, 2017

Could this perhaps also include a json key to indicate whether the artifact was just compiled or not?

Added a "fresh" key

@alexcrichton
Copy link
Member

@bors: r+

@bors
Copy link
Contributor

bors commented Feb 26, 2017

📌 Commit 7bfd7dc has been approved by alexcrichton

@bors
Copy link
Contributor

bors commented Feb 26, 2017

⌛ Testing commit 7bfd7dc with merge 338c7b7...

@bors
Copy link
Contributor

bors commented Feb 26, 2017

💔 Test failed - status-appveyor

@matklad
Copy link
Member Author

matklad commented Feb 27, 2017

@bors: retry

@bors
Copy link
Contributor

bors commented Feb 27, 2017

⌛ Testing commit 7bfd7dc with merge 3526d8f...

bors added a commit that referenced this pull request Feb 27, 2017
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`).
@bors
Copy link
Contributor

bors commented Feb 27, 2017

☀️ Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 3526d8f to master...

@bors bors merged commit 7bfd7dc into rust-lang:master Feb 27, 2017
@matklad matklad deleted the always-artifacts branch March 27, 2017 10:04
@ehuss ehuss added this to the 1.17.0 milestone Feb 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants