-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Upload linux-x86_64 artifacts on try branch. #42418
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
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
.travis.yml
Outdated
if [ "$ALLOW_PR" = "" ] && [ "$TRAVIS_BRANCH" != "auto" ]; then | ||
export RUN_SCRIPT="echo 'skipping, not a full build'"; | ||
else | ||
if [[ "$ALLOW_PR" = "1" || "$TRAVIS_BRANCH" == "auto" || ( "$ALLOW_TRY" = "1" && "$TRAVIS_BRANCH" = "try" ]; then |
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.
The (
appears to be unclosed.
@bors try |
⌛ Trying commit abb50f2 with merge 69feff5... |
.travis.yml
Outdated
SKIP_BUILD=true | ||
fi | ||
# Otherwise, do the build if we are on the auto branch, or the try branch and $ALLOW_TRY == 1 | ||
elif [[ "$TRAVIS_BRANCH" == "auto" || ( "$ALLOW_TRY" == "1" || "$TRAVIS_BRANCH" == "try" ) ]]; then |
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.
Allow try && try branch
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.
Actually, no, this is correct. Never mind.
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.
Your first comment was correct.
Can somebody trigger another try run of this before landing, to check that the build starts? Once the |
The artifacts got successfully uploaded to |
417c3b1
to
7994e1a
Compare
This saves us builders for more helpful purposes.
@bors try |
Upload linux-x86_64 artifacts on try branch. This is an experiment to explore generating artifacts for testing with cargobmomb. See rust-lang/crater#64.
I don't know of homu is supposed to print something, but try succeeded. I guess that makes this successful -- r? @alexcrichton for final sign off though. |
Here are the builds:
As this merges,
|
Actually, I believe @alexcrichton gave approval over IRC yesterday. @bors r+ |
📌 Commit d2ff798 has been approved by |
@bors retry |
Upload linux-x86_64 artifacts on try branch. This is an experiment to explore generating artifacts for testing with cargobmomb. See rust-lang/crater#64.
☀️ Test successful - status-appveyor, status-travis |
This is an experiment to explore generating artifacts for testing with cargobmomb. See rust-lang/crater#64.