Open Bug 1312343 Opened 8 years ago Updated 2 years ago

make sure the sync health dashboards would be capable of noticing our recent nserror/1 regression

Categories

(Firefox :: Sync, defect, P3)

Product:
Firefox
Component:
Sync
Type:
defect

Tracking

()

People

(Reporter: markh, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [sync-quality][sync-metrics]) 

Best we can tell, bug 1274496 caused a spike in bookmark engine failures for a small but significant number of users. This was apparently fixed by bug 1310525. It was reported as { code: "nserror", value: 1 } error.

FTR, the first build ID with that problem was 20160915030417, and the last was 20161019.

It would be absolutely perfect if our health dashboards were able to detect and flag this kind of regression and notice the fix - one that doesn't break most users, but still breaks enough to throw the engine failure count up significantly.

(Note that I think they are heading in this direction, but this particular bug seems a good test-case, so I'm opening this bug while I have the details paged in)
Priority: -- → P3
Depends on: 1314501
Blocks: 1314501
No longer depends on: 1314501
Blocks: 1237824
Whiteboard: [sync-quality][sync-metrics]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.