Open Bug 1423573 Opened 8 years ago Updated 3 years ago

Stop marking CPU/IO usage stats as TinderboxPrints in automation logs

Categories

(Firefox Build System :: General, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: emorley, Unassigned)

References

Details

Hi! In bug 1342296 we're trying to reduce the amount of spurious database entries in the Treeherder JobDetails table, and would like to stop marking the CPU/IO usage stats in log output with TinderoxPrint, since: * they are already ingested into Perfherder * people can still look at the string in the logs even if it's not surfaced in the "Job Details" panel As far as I can tell, these come from: https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/mozharness/base/python.py#696-739
Product: Core → Firefox Build System

Hi, I'm not sure if this bug is still applicable but we will stop parsing TinderboxPrint lines by April 30th so if you are not reporting these stats to Perfherder you will want to do so before then (let me know if you need a longer time frame to do so).

Flags: needinfo?(rstewart)

glob -- do you have context on this request? I don't have enough context on telemetry at Mozilla to have context on what the request means, how much work it would take on our end, etc. Since we were talking about telemetry anyway I wanted to just make sure this was on your radar.

Flags: needinfo?(rstewart) → needinfo?(glob)

(In reply to Ricky Stewart from comment #2)

glob -- do you have context on this request? I don't have enough context on telemetry at Mozilla to have context on what the request means, how much work it would take on our end, etc. Since we were talking about telemetry anyway I wanted to just make sure this was on your radar.

I don't have any context here. However it looks like an attempt to gather some form of telemetry before mach was hooked up to The Telemetry System.

The most I know is that this data doesn't make its way to sql.telemetry.m.o.

Flags: needinfo?(glob)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.