Linux builds don't respect log folding messages #7262
Comments
|
I'm seeing the same thing Mac fold fine Linux doesn't |
|
@agc93 Your Linux build https://api.travis-ci.org/jobs/197297726/log.txt does not have any marker that Mac one does https://api.travis-ci.org/jobs/197297727/log.txt. (Search for @devlead Yours looks the same. |
|
I'm guessing that these compiled binary files |
|
@BanzaiMan I'm not using that module, but we're both using Cake build scripts, I'll try to add some more debug output. Strange thing is that it has worked, it's the same build script for Mac & Linux. By looking at code , the current theory would be not identifying that it's running under Travis, but that's just checking that the environment variable |
|
|
|
@BanzaiMan I've just run the exact same script locally on a Fedora 25 machine after setting Anyone can replicate the messages by cloning the repo, setting a non-empty value to |
|
Tracvis does get identified correctly, see here on Linux
Still waiting for Mac build to start. The raw log does seem truncated/transformed though some |
|
Mac folded - in a good way. |
|
Interesting tee:ing the log solves the issue, So it would seem to be an issue that it's likely (as tee strips that info) Travis's having issues with the colorized log on Linux, but it works on Mac. |
|
Looks like the raw log indead is mangled on several places when not tee:ing i.e. comparing And there's several places like that, which can be spotted in the log. On Mac same thing works regardless of tee:ing or not. |
|
Did a gist comparing raw unbuffered log with travis raw log So the service messages are clearly there, although with an escape sequence, but raw log indeed seems filtered. |
|
@BanzaiMan any chance we'll see a fix to support folding regardless of any escape sequences? |
|
@BanzaiMan also would be nice if the raw log wasn't truncated, can be a real wild goose chase troubleshooting if certain details are omitted from the log. |
|
@BanzaiMan Any progress on this one? Log folding is very useful for long logs but extremely limiting to use in its current state. |
|
Sorry, but we do not have updates to share. |
|
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues |
Injecting code folding messages using the following format:
works on OS X/macOS builds, but does not work for Linux builds. For example, this build includes the exact same build (with the exact same log output) on both and while log-based folding works correctly on the macOS build (starts on line 229), it doesn't appear to function at all for the Linux build (should start on line 1184, but doesn't).
The service/command messages do not appear in the Linux build's log output so they are clearly being identified/detected by Travis, just the folding is not kicking in.
The text was updated successfully, but these errors were encountered: