Closed
Bug 1541957
Opened 5 years ago
Closed 5 years ago
geckoview tests running in non-e10s mode
Categories
(Testing :: General, defect)
Tracking
(firefox68 fixed)
RESOLVED
FIXED
mozilla68
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: gbrown, Assigned: ahal)
References
Details
Attachments
(1 file)
geckoview mochitests and reftests on Android 7.0 x86_64 have been running in e10s mode, but this changed recently:
Assignee | ||
Comment 3•5 years ago
|
||
My mistake, I naively assumed that all geckoview tasks had geckoview
in their label somewhere:
https://hg.mozilla.org/integration/autoland/rev/486395fabe66f79ab3fcfc3b95c214d4957f7f8b#l5.74
I'll get a fix up soon.
Assignee: nobody → ahal
Status: NEW → ASSIGNED
Flags: needinfo?(ahal)
Assignee | ||
Comment 4•5 years ago
|
||
Hm, looks like there's no mention of "geckoview" in the entire task definition except for in the target name (which is what the previous filtering was doing). I guess I'll go back to using that for now, but it would be good to have more of an ability to filter based on mobile app.
Maybe we can add a mobile_project = {fennec, geckoview, refbrow, fenix}
attribute or something. Good follow-up fodder.
Assignee | ||
Comment 5•5 years ago
|
||
Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b948a38f204a [ci] Fix regression causing geckoview tests to run without e10s, r=gbrown
Comment 7•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in
before you can comment on or make changes to this bug.
Description
•