Travis: Add a tool to print timestamp in front of log messages #40577
Comments
retep998
pushed a commit
to alexcrichton/rust
that referenced
this issue
Mar 21, 2017
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
|
You probably just want to use |
bors
added a commit
that referenced
this issue
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Often when debugging travis logs it's difficult to see how long everything is taking as we only time some steps, not all. Additionally there's not a lot of information to see how long it takes between steps.
It'd be awesome if we had a tool where we basically wrapped the entire build (
src/ci/run.sh) in a process that simply prepended all stdout/stderr messages with a relative timestamp. AppVeyor does this by default (has a timestamp for each log line message) but unfortunately Travis doesn't.Apparently Julia has something like this which ends up looking like https://travis-ci.org/JuliaLang/julia/jobs/211627387#L370 which is basically exactly what we'd want.
The text was updated successfully, but these errors were encountered: