travis: Add timestamps to all build messages#40605
Merged
Merged
Conversation
Contributor
|
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
Member
Author
|
Note that this PR also disables |
Contributor
|
@bors r+ |
Collaborator
|
📌 Commit 4b25ccd has been approved by |
Collaborator
|
☔ The latest upstream changes (presumably #40575) made this pull request unmergeable. Please resolve the merge conflicts. |
alexcrichton
force-pushed
the
add-stamps
branch
from
4b25ccd to
fd6cffc
Compare
Member
Author
|
@bors: r=brson |
Collaborator
|
📌 Commit fd6cffc has been approved by |
Contributor
|
@bors r- https://travis-ci.org/rust-lang/rust/jobs/213256348 |
alexcrichton
force-pushed
the
add-stamps
branch
from
fd6cffc to
499fb8d
Compare
Member
Author
|
@bors: r=brson |
Collaborator
|
📌 Commit 499fb8d has been approved by |
Collaborator
|
🔒 Merge conflict |
When debugging why builds are taking so long it's often useful to get the timestamp of all log messages as we're not always timing every tiny step of the build. I wrote a [utility] for prepending a relative timestamp from the start of a process which is now downloaded to the builders and is what we wrap the entire build invocation in. [utility]: https://github.com/alexcrichton/stamp-rs Closes rust-lang#40577
This makes travis problems more difficult to debug, so let's just enable more verbose logging.
Contributor
|
@bors r=brson |
Collaborator
|
📌 Commit 2727866 has been approved by |
Collaborator
bors
added a commit
that referenced
this pull request
Mar 23, 2017
travis: Add timestamps to all build messages When debugging why builds are taking so long it's often useful to get the timestamp of all log messages as we're not always timing every tiny step of the build. I wrote a [utility] for prepending a relative timestamp from the start of a process which is now downloaded to the builders and is what we wrap the entire build invocation in. [utility]: https://github.com/alexcrichton/stamp-rs Closes #40577
Collaborator
|
☀️ Test successful - status-appveyor, status-travis |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
When debugging why builds are taking so long it's often useful to get the
timestamp of all log messages as we're not always timing every tiny step of the
build. I wrote a utility for prepending a relative timestamp from the start of
a process which is now downloaded to the builders and is what we wrap the entire
build invocation in.
Closes #40577