Closed Bug 1596347 Opened 1 year ago Closed 4 months ago

Investigate perf data produced by job_resource_usage

Categories

(Tree Management :: Perfherder, defect, P3)

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: igoldan, Assigned: sclements)

References

Details

We need to investigate one of the data producers. Namely, data related to the job_resource_usage. We need to find out if it should be updated or deactivated.

Background

Perfherder is attempting to ingest perf data from the job_resource_usage framework.

That framework isn't officially registered and we're having tons and tons of Performance framework job_resource_usage does not exist, skipping load of performance artifacts log lines because of that.

Quickly skimming the mozilla-central source code, it seems that the data producer code is around this source/testing/mozharness/mozharness/base/python.py line, associated to bug 1272176.

Severity: normal → minor
Priority: -- → P3

I'm trying to clean up the logging the log_parser does. Do you know who needs to be contacted about this?

Flags: needinfo?(igoldan)

Bug 1272176 added it. The original author is no longer at Mozilla.
I see that Jordan Lund is the triage owner for the related component, so might want to contact him.

Flags: needinfo?(igoldan)
Depends on: 1634123

Per the conversation in bug 1634123, I'll submit a pr so that we don't log the job_resource_usage framework. Kyle would like to keep it's current setup for active data usage in case it might be useful in the future.

Assignee: nobody → sclements
Status: NEW → ASSIGNED

I'm not seeing this show up in the logs anymore. I suspect it's because of how we've changed our logging levels.

Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.