Too much tests are ran with mach try
Categories
(Testing :: General, defect)
Tracking
(firefox-esr115 unaffected, firefox122 unaffected, firefox123 unaffected, firefox124 unaffected, firefox125 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox122 | --- | unaffected |
| firefox123 | --- | unaffected |
| firefox124 | --- | unaffected |
| firefox125 | --- | fixed |
People
(Reporter: calixte, Assigned: jmaher)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
In the last try I ran:
https://treeherder.mozilla.org/jobs?repo=try&revision=cde41d90cbd79d86c5b8efcf6dc8266e1a3dd32f
a bunch of tests have been triggered.
And usually there are a way less triggered tests::
https://treeherder.mozilla.org/jobs?repo=try&revision=f62a6288e338e97c189e097275363dfeee169e40
In both cases, the mach command was exactly the same:
./mach try fuzzy -q "'debug | 'opt" browser/base/content/test/static toolkit/components/pdfjs/test
| Assignee | ||
Comment 1•2 years ago
|
||
the problem is here we are not sending the specific chunk numbers to the decision task, instead we are sending the -* wildcard. This was introduced as a feature in bug 1876350 and we need to account for additional parameters that would "filter" tasks and do that on the client end. Also some unittests would be solid
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1876350
Comment 3•2 years ago
|
||
Set release status flags based on info from the regressing bug 1876350
| Assignee | ||
Comment 4•2 years ago
|
||
Updated•2 years ago
|
Comment 6•2 years ago
|
||
| bugherder | ||
Comment 7•2 years ago
|
||
The patch landed in nightly and beta is affected.
:jmaher, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox124towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•2 years ago
|
Description
•