Closed
Bug 1846471
Opened 2 years ago
Closed 2 years ago
[Experiment] The client is not enrolled in an experiment that has another experiment excluded
Categories
(Firefox for Android :: Experimentation and Telemetry, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: vbandac, Assigned: beth)
References
Details
[Prerequisites]:
- Have a new experiment (EXP0) in preview that has a 2nd experiment (EXP1) added as an “Excluded Experiment”.
- If Excluded, make sure that the user was never enrolled in the past or present in that experiment in order to be able to enroll in the tested experiment / rollout.
[Steps to reproduce]:
- Install and open the latest Firefox Nightly, go to settings and activate the secret menu.
- From the secret menu, go to “Secret settings” and activate “Use Nimbus Preview Collection”.
- Fully close Firefox and reopen it a couple of times.
- Navigate to the “Nimbus experiments” and observe the page.
[Expected result]:
- The user is NOT enrolled in EXP1 but is enrolled in EXP0.
[Actual result]:
- The user is not enrolled in any of the experiments.
[Device name]:
- OnePlus 6
- Samsung A53 5G
- Google Pixel 5
[Android version]:
- Android 11, Android 13
[Firefox version]:
- Firefox Nightly 117.0a1 - Build ID: 2015965307, c2a721d16b, GV: 117.0a1 - 20230729205741, AS: 117.20230729050233
[Notes]:
- For this experiment we used a custom build to target the Preview collection from the Stage server.
- The issue is NOT reproducible with required experiments.
- This issue is NOT reproducible on Desktop, using the same set-up.
- This issue also affects experiments with both required and excluded in the targeting expression.
| Assignee | ||
Comment 1•2 years ago
|
||
This was fixed in https://github.com/mozilla/experimenter/pull/9204
Assignee: nobody → brennie
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 2•2 years ago
|
||
I have verified that this issue is no longer reproducible. I am marking this issue as Verified Fixed.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•