Open Bug 1620339 Opened 6 years ago Updated 3 years ago

make it easy/automatic to run likely-to-fail mochitests

Categories

(Firefox :: Messaging System, task, P3)

task

Tracking

()

Tracking Status
firefox75 --- wontfix
firefox76 --- affected

People

(Reporter: dmosedale, Unassigned)

References

(Blocks 1 open bug)

Details

In the GitHub repo, we had a special taskcluster docker image that run mochitests for us on every PR, which made for a super tight feedback loop . Now that we're back in m-c, the general infrastructure is that we land something through Phab/Lando, and then if the mochitests fail, it gets backed out.

It would be nice to at least transmogrify the script that we have (browser/components/newtab/mochitest.sh) so that it works correctly locally. Or, alternately, Mardak says he has a similar local script that maybe we should just use to replace the existing mochitest.sh. Both of these scripts run our own mochitests, plus a list of mochitests on things tightly coupled to our work that fail semi-regularly when we make some change.

Markdak also pointed out that such a thing could be implemented in a way that works broadly across m-c (eg mach test-related), but that probably wants to be a spin-off of this bug.

Priority: -- → P2
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.