Closed Bug 1662499 Opened 4 years ago Closed 3 years ago

Reduce CI tests timeout value on Pixels once Cranelift is faster to compile

Categories

(Core :: JavaScript: WebAssembly, task, P5)

Product:
Core
Component:
JavaScript: WebAssembly
Type:
task

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: bbouvier, Unassigned)

References

Details

In bug 1660944, the timeout value to run the CI tests on Android Pixels phones was raised because wasm tests would take more time to run. If Cranelift gets faster at compiling, and the generated code gets faster to run, it is possible that we could reset the timeout value to what it was before. Alternatively, if the slowdown can't be avoided, we could resort to splitting the jit-test tests collection into more chunks, and keep the lower timeout value, as suggested by gbrown.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.