Closed Bug 1657142 Opened 7 months ago Closed 6 months ago

High schema error rates for `environment/system/gfx/adapters/N/GPUActive`

Categories

(Data Platform and Tools :: General, defect, P2)

defect
Points:
1

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: frank, Assigned: amiyaguchi)

References

Details

(Whiteboard: [data-quality])

Attachments

(2 files)

This dashboard shows schema error rates. We're tracking an error in the environment at GPUActive. It looks like this really started increasing over the past few weeks, and the voice ping (which is, albeit, a very tiny pop) is disproportionately affected. However the main, event, and rest of the telemetry pings are also affected.

Chutten, do you know of any changes to this field that could cause this?

Flags: needinfo?(chutten)

Ohhhh, I see. It'll be bug 1651425

For setups where there are more than 2 GPUs, we now report all of them instead of just the first 2. Unfortunately the code responsible for GPUActive wasn't updated at the same time so it only supplies a value for the first two.

As a result I expect any ping coming from a Environment with more than two GPUs will be invalid (because it's missing that field).

Guess the correct person to ni? from the people responsible there would be.... jgilbert? How would you like to proceed?

Flags: needinfo?(chutten) → needinfo?(jgilbert)
Regressed by: 1651425
Points: --- → 1
Priority: -- → P2
Assignee: nobody → amiyaguchi

The number of errors drops abruptly on 2020-08-20, which corresponds to the deploy date of the PR. I'll be filing a follow up bug for potential backfill.

https://sql.telemetry.mozilla.org/queries/74258#185635

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Blocks: 1661565
Flags: needinfo?(jgilbert)

(In reply to Chris H-C :chutten from comment #2)

Ohhhh, I see. It'll be bug 1651425

It doesn't look like this patch actually landed. It's reviewed, but the bug is still open and I don't see a checkin comment.

You're right. What the heck.

Lessee, what changes have there been to GPU Active? The only change more recent than 2016 was Bug 1676883 which was last November, far after the problem was first noticed.

It's a mystery.

No longer regressed by: 1651425
You need to log in before you can comment on or make changes to this bug.