Closed
Bug 1128003
Opened 10 years ago
Closed 7 years ago
Experiments: ensure that experiments can withstand manifest changes in sample, endTime, maxRunningSeconds
Categories
(Firefox Health Report Graveyard :: Client: Desktop, defect, P4)
Firefox Health Report Graveyard
Client: Desktop
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Felipe, Unassigned)
Details
(Whiteboard: [measurement:client])
It will probably come in handy in the future the ability to change the sampling size of a running experiment (to release it gradually, or increase or reduce sampling as necessary, according to data coming in), and to extend or shorten the length of an experiment by changing the endTime or maxRunningSeconds.
In one of the earlier experiments I suggested starting with a small sample size and changing it later, but as it was something that wasn't tried before, we didn't want to do it live to figure out.
It may well be that all of this works, but it would be nice to have existing evidence of that (and test coverage) to ensure we can do this with peace of mind whenever it becomes necessary.
Comment 1•10 years ago
|
||
They *should* get re-evaluated properly.
We can rather easily add test-coverage here:
browser/experiments/test/xpcshell/test_api.js
Updated•9 years ago
|
Priority: -- → P4
Whiteboard: [measurement:client]
Comment 2•7 years ago
|
||
Telemetry experiments were removed from Firefox per bug 1415284.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•