Re: [tracecompass-dev] Hudson console logs bloated with warnings

[Matthew Khouzam <matthew.khouzam@xxxxxxxxxxxx>]

I thought it was occurring 100% of the time, 24/7 all day, every day.

It is due to us adding lost events to the trace. These are legit issues, I suggest converting them to tracecompass log stuff so it is not as visible in CI but still available.

Is that OK?

---

From: tracecompass-dev-bounces@xxxxxxxxxxx <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx>
Sent: Friday, May 26, 2017 11:06:09 AM
To: tracecompass developer discussions
Subject: Re: [tracecompass-dev] Hudson console logs bloated with warnings

 

This has been happening for quite a long time. I have the feeling it's a legit but intermittent bug. Worth looking into I think.

Marc-André

---

From: tracecompass-dev-bounces@xxxxxxxxxxx <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of Patrick Tasse <patrick.tasse@xxxxxxxxx>
Sent: Friday, May 26, 2017 11:00:32 AM
To: tracecompass developer discussions
Subject: [tracecompass-dev] Hudson console logs bloated with warnings

 

Hi,

Some Hudson console logs contain over 135K lines (34MB) of warning messages from org.eclipse.tracecompass.analysis.linux.core (KernelCpuUsageAnalysis):

https://hudson.eclipse.org/tracecompass/job/tracecompass-gerrit/13683/consoleFull

While some console logs do not:

https://hudson.eclipse.org/tracecompass/job/tracecompass-gerrit/13682/consoleFull

Does anyone know why there is a difference, and if it can be avoided?

Thanks,

Patrick