Restrict gv-junit-e10s-multi to integration and m-c
Categories
(GeckoView Graveyard :: Sandboxing, task, P1)
Tracking
(firefox77 wontfix, firefox78 fixed)
People
(Reporter: bugzilla, Assigned: bugzilla)
References
Details
(Whiteboard: [geckoview:m78])
Attachments
(2 files, 2 obsolete files)
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta-
|
Details | Review |
Sheriffs are concerned when there are failures on beta. Let's restrict this test suite to mozilla-central
until e10s-multi is ready to ride the trains.
Assignee | ||
Comment 1•4 years ago
|
||
Oh, and integration trees.
Assignee | ||
Comment 2•4 years ago
|
||
I think I did this right?
Until we ride the trains, we only want to run this suite for integration
branches, mozilla-central
, and try
pushes.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
|
||
Comment on attachment 9150254 [details]
Bug 1639334: Restrict gv-junit-e10s-multi test suite to trunk and try; r=gbrown
Beta/Release Uplift Approval Request
- User impact if declined: No user impact, this is to remove a test suite that is not currently needed on beta and release.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Change to taskgraph configuration involving test suite that is not currently riding the trains.
- String changes made/needed:
Comment 5•4 years ago
|
||
bugherder |
Comment 6•4 years ago
|
||
Comment on attachment 9150254 [details]
Bug 1639334: Restrict gv-junit-e10s-multi test suite to trunk and try; r=gbrown
thanks.
Comment 7•4 years ago
|
||
bugherder uplift |
Comment 9•4 years ago
|
||
Assignee | ||
Comment 10•4 years ago
|
||
Tom, I see your comment -- do you know what's going on here? Can we resolve this bug and file a follow-up, or is there still something that needs to be landed here?
Comment 11•4 years ago
|
||
The original patch add run-on-projects
to TEST_VARIANTS
, but nothing
currently looks at that. Move it into a replace
block, which gets merged with
the task definition.
This is enough to handle this specific change, but if more control is needed
per-test, we should revisit how this is handled. Fission supports
fission-run-on-projects
and fission-tier
to override those values based on
the variants, but it would probably make sense to generalize those to have more
general way of specifying variant-specific configuration.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 12•4 years ago
|
||
Comment 13•4 years ago
|
||
bugherder |
Assignee | ||
Comment 14•4 years ago
|
||
Comment on attachment 9151617 [details]
Bug 1639334: Set run-on-projects
for gv-junit-e10s-multi
correctly; r?ahal
Beta/Release Uplift Approval Request
- User impact if declined: Test suites running in beta for a non-shipped configuration.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Trivial patch, taskgraph fix.
- String changes made/needed:
Comment 15•4 years ago
|
||
Comment on attachment 9151617 [details]
Bug 1639334: Set run-on-projects
for gv-junit-e10s-multi
correctly; r?ahal
78 merged to beta today and already has this
Updated•4 years ago
|
Comment 16•4 years ago
|
||
Updated•4 years ago
|
Comment 17•2 years ago
|
||
Moving some e10s bugs to the new GeckoView::Sandboxing component.
Updated•4 months ago
|
Description
•