Make '1proc' a test variant rather than a special cased e10s attribute
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(firefox97 fixed)
Tracking | Status | |
---|---|---|
firefox97 | --- | fixed |
People
(Reporter: ahal, Assigned: ahal, Mentored)
References
Details
Attachments
(4 files)
We currently run a bunch of '1proc' test tasks. These are currently handled by a special case e10s
flag, but they should just be a standard variant.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Previously we we're validating the entire 'test_description_schema' again, even
though the vast majority of those keys were in fact no longer needed. This was
preventing us from ever removing keys from the 'task' object. Which I believe
is a good practice to keep things simple.
Assignee | ||
Comment 2•4 years ago
|
||
This replaces the 'e10s' key with a standard variant in task configuration.
Depends on D133222
Assignee | ||
Comment 3•4 years ago
|
||
Tasks that set this key to false will not run under the standard no variant
configuration.
This is needed to replace the 'e10s=false' case (i.e tasks that only run with
1proc like mochitest-chrome or mochitest-a11y.
Depends on D133224
Assignee | ||
Comment 4•4 years ago
|
||
This attribute isn't necessary as e10s is the default. Instead consumers can
check if the string '1proc' appears in the unittest_variant attribute.
Depends on D133225
Assignee | ||
Updated•4 years ago
|
![]() |
||
Comment 7•4 years ago
|
||
bugherder |
Assignee | ||
Updated•4 years ago
|
Comment 9•4 years ago
|
||
bugherder |
Description
•