Open Bug 1834620 Opened 3 years ago Updated 2 years ago

AboutWelcome and Spotlight browser-chrome tests have unstable ordering

Categories

(Firefox :: Messaging System, task, P3)

task

Tracking

()

People

(Reporter: chutten, Unassigned)

References

Details

We had some difficulty writing tests for bug 1825863 as we expected the ordering of events (IMPRESSION, CLICK, DISMISS, etc) to be consistent. The order that AWPage:TELEMETRY_EVENT events comes in isn't stable from local development to CI or from normal test runs to --verify or sometimes even between runs within the same environment.

This bug is about diagnosing if the event order is unstable in the real world as well as in tests (which should be discernable from the instrumentation added in bug 1825863 (hint: use ping_info.seq to uncover the order)), determining if it can or should be made stable within tests, and adjusting the tests should the order be found to be able to be made stable.

(( Please coordinate with the PingCentre Replacement Project (find :chutten, he's normally around) before landing changes to instrumentation. ))

Also: don't forget to un-skip-if browser_multistage_spotlight_telemetry.js for verify runs should we find ourselves able to stabilize the order.

The first step, I think, will be to look at the collected telemetry from that bug once it lands...

Assignee: nobody → dmosedale
Iteration: --- → 116.1 - June 5 - June 16
Priority: -- → P1
Iteration: 116.1 - June 5 - June 16 → 116.2 - June 19 - June 30
Priority: P1 → P2
Iteration: 116.2 - June 19 - June 30 → 117.1 - July 3 - July 14
Iteration: 117.1 - July 3 - July 14 → 117.2 - July 17 - July 28
Iteration: 117.2 - July 17 - July 28 → 118.1 - July 31 - Aug 11
Iteration: 118.1 - July 31 - Aug 11 → 118.2 - Aug 14 - Aug 25
Iteration: 118.2 - Aug 14 - Aug 25 → 119.1 - Aug 28 - Sept 8
Iteration: 119.1 - Aug 28 - Sept 8 → 119.2 - Sept 11 - Sept 22
Iteration: 119.2 - Sept 11 - Sept 22 → ---
Assignee: dmosedale → nobody
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.