-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
ci: Reenable step timings on AppVeyor #61489
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(rust_highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
label
Jun 3, 2019
pietroalbini
reviewed
Jun 3, 2019
This was accidentally regressed in rust-lang#60777 by accident, and we've stopped printing out step timings on AppVeyor recently reducing the ability for us to track build times over time!
alexcrichton
force-pushed
the
appveyor-timings
branch
from
June 3, 2019 14:50
8db3670
to
b87bad7
Compare
@bors r+ rollup |
📌 Commit b87bad7 has been approved by |
bors
added
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
and removed
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
labels
Jun 3, 2019
Centril
added a commit
to Centril/rust
that referenced
this pull request
Jun 4, 2019
…etroalbini ci: Reenable step timings on AppVeyor This was accidentally regressed in rust-lang#60777 by accident, and we've stopped printing out step timings on AppVeyor recently reducing the ability for us to track build times over time!
Centril
added a commit
to Centril/rust
that referenced
this pull request
Jun 4, 2019
…etroalbini ci: Reenable step timings on AppVeyor This was accidentally regressed in rust-lang#60777 by accident, and we've stopped printing out step timings on AppVeyor recently reducing the ability for us to track build times over time!
Centril
added a commit
to Centril/rust
that referenced
this pull request
Jun 4, 2019
…etroalbini ci: Reenable step timings on AppVeyor This was accidentally regressed in rust-lang#60777 by accident, and we've stopped printing out step timings on AppVeyor recently reducing the ability for us to track build times over time!
bors
added a commit
that referenced
this pull request
Jun 4, 2019
Rollup of 13 pull requests Successful merges: - #61135 (Fix documentation of `Rc::make_mut` regarding `rc::Weak`.) - #61404 (miri unsizing: fix projecting into a field of an operand) - #61409 (Fix an ICE with a const argument in a trait) - #61413 (Re-implement async fn drop order lowering ) - #61419 (Add an unusual-conversion example to to_uppercase) - #61420 (Succinctify splice docs) - #61444 (Suggest using `as_ref` on `*const T`) - #61446 (On TerminatorKind::DropAndReplace still handle unused_mut correctly) - #61485 (azure: retry s3 upload if it fails) - #61489 (ci: Reenable step timings on AppVeyor) - #61496 (Do not panic in tidy on unbalanced parentheses in cfg's) - #61497 (Treat 0 as special value for codegen-units-std) - #61499 (Add regression test for existential type ICE #53457) Failed merges: r? @ghost
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was accidentally regressed in #60777 by accident, and we've stopped
printing out step timings on AppVeyor recently reducing the ability for
us to track build times over time!