So given recent discussions I attempted to run mach jit-test --slow locally, and discovered at least one test case which has been broken for a while (Bug 1841118)

The following tests also timed out:

auto-regress/bug701332.js
auto-regress/bug746103.js
basic/createMandelSet.js
basic/testCompileScript.js

I don't really know how, but it feels like we should run jit-test --slow on some less-than-every-build frequency as a tier 3 job so that we can eventually catch breakage.

In a debug configuration, ./mach jit-test --slow took 818.3s for me on my M1 MBP.

(In reply to Matthew Gaudet (he/him) [:mgaudet] from comment #0)
Maybe we could make one of the builds an optdebug configuration.