Bug #4840: Jenkins build logs are unreadable - NFD - NDN project issue tracking system

Actions

Copy link

Bug #4840

closed

Jenkins build logs are unreadable

Added by Davide Pesavento about 5 years ago. Updated about 4 years ago.

Status:

Closed

Priority:

Low

Assignee:

Category:

Build

Target version:

Start date:

Due date:

% Done:

100%

Estimated time:

Description

Compilation errors and warning messages are all messed up in the "consoleFull" logs of jenkins builds. As far as I can see, all Ubuntu slaves are affected, OSX slaves do not seem to be affected.

This is just one example, taken from http://jenkins.named-data.net/job/ndn-cxx/6793/OS=Ubuntu-18.04-64bit/consoleFull

[K../ndn-cxx/interest.cpp:436:[Kwarnin[Kconst ndn::Exclude& ndn::Interest::getExclude() co[K’ is deprecate[K-Wdeprecated-declarati[K]
   if (!getExclude([K.empty() &&
                   [K
In file included from [K../ndn-cxx/interest.cpp:2[K:
[K../ndn-cxx/interest.hpp:411[Knot[Kdeclared here
   [KgetExcl[K() const
   [K^~~~~~~[K

This is not a new or recent issue, it started happening a few months ago (not sure when exactly).

Actions

Copy link

Updated by Davide Pesavento about 5 years ago

The "consoleText" plain text logs have the same problem, but in a lot more places: not only compiler warnings/errors are messed up, but practically every line printed by waf or Boost.Test contains extraneous characters (they look like ANSI escape codes). In this case all slaves are affected, both Ubuntu and OSX. Examples:

http://jenkins.named-data.net/job/ndn-cxx/6793/OS=OSX-10.14/consoleText
http://jenkins.named-data.net/job/ndn-cxx/6793/OS=Ubuntu-18.10-64bit/consoleText

Actions

Copy link

Updated by Md Ashiqur Rahman about 5 years ago

Davide Pesavento wrote:

The "consoleText" plain text logs have the same problem, but in a lot more places: not only compiler warnings/errors are messed up, but practically every line printed by waf or Boost.Test contains extraneous characters (they look like ANSI escape codes). In this case all slaves are affected, both Ubuntu and OSX. Examples:

http://jenkins.named-data.net/job/ndn-cxx/6793/OS=OSX-10.14/consoleText
http://jenkins.named-data.net/job/ndn-cxx/6793/OS=Ubuntu-18.10-64bit/consoleText

Yes. The console text output has been looking garbled right after we added the 18.10 or upgraded to Jenkins version 2.158 (That's just about 2 months ago). I think at that time, only the compilation outputs had a "square" symbol in compilation stage, but now this has become more severe. I'm looking into it.

Actions

Copy link

Updated by Davide Pesavento about 5 years ago

Status changed from New to In Progress
Assignee changed from Md Ashiqur Rahman to Davide Pesavento

Actions

Copy link

Updated by Davide Pesavento about 5 years ago

% Done changed from 0 to 20

I believe this is a regression in the ansicolor jenkins plugin. Reported upstream: https://github.com/jenkinsci/ansicolor-plugin/issues/151

Actions

Copy link

Updated by Davide Pesavento almost 5 years ago

Status changed from In Progress to Feedback
Assignee deleted (~~Davide Pesavento~~)
Priority changed from Normal to Low

The ansicolor plugin developers don't seem in any hurry to fix this bug, I guess it doesn't impact their current uses. Sad. Unless someone else steps up and contributes a patch, I doubt this will get fixed any time soon. Unassigning myself, as there isn't much I can do at the moment.

Actions

Copy link