Combination of --update-intermittent and --full is surprising
Categories
(Testing :: web-platform-tests, defect, P1)
Tracking
(firefox70 fixed)
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: jgraham, Assigned: nikkis)
References
Details
Attachments
(1 file)
--update-intermittent
should add new intermittents to the existing list, or create a list if there isn't one. --full
should remove annotations for configurations that don't exist any longer. But --update-intermittent
with --full
is currently removing all the existing annotations and then adding only intermittents seen in the new results, causing unexpected data loss e.g.
[foo.html]
expected: [TIMEOUT, OK]
with a new set of results showing ERROR
and OK
will end up as
[foo.html]
expected: [ERROR, OK]
rather than as e.g.
[foo.html]
expected: [ERROR, TIMEOUT, OK]
Reporter | ||
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
•
|
||
I've tried to reproduce this bug locally but everything seems to be working as it should when --update-intermittent
and --full
are used together. May I see which logs/tests you used?
I suspect here is where we will need to make adjustments. https://searchfox.org/mozilla-central/source/testing/web-platform/tests/tools/wptrunner/wptrunner/manifestupdate.py#563
Although, new_value = self.updated_value(current_value, nodes[0].result_values)
should already take --update-intermittent
into account...
Assignee | ||
Comment 2•6 years ago
|
||
When update_intermittent
is True and remove_intermittent
is False,
ensure full_update
does not remove any existing intermittent statuses
from tests with conditions.
Comment 3•6 years ago
|
||
The priority flag is not set for this bug.
:jgraham, could you have a look please?
For more information, please visit auto_nag documentation.
Reporter | ||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 5•6 years ago
|
||
bugherder |
Comment 10•5 years ago
|
||
bugherder |
Description
•