Closed Bug 1914577 Opened 1 year ago Closed 11 months ago

High number of intermittent jittest failures

Categories

(Core :: JavaScript Engine, defect, P1)

defect

Tracking

()

RESOLVED FIXED
132 Branch
Tracking Status
firefox132 --- fixed

People

(Reporter: jonco, Assigned: bvisness)

References

(Blocks 1 open bug, Regressed 1 open bug)

Details

Attachments

(2 files, 2 obsolete files)

For a while we've had a high inflow of intermittent jittest failures. There are currently 287 open with half of thosed opened this year:

https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&component=JavaScript%20Engine&j3=OR&o8=substring&o1=notequals&f11=CP&v1=Graveyard&f2=OP&v8=intermittent&f6=alias&o5=substring&v5=intermittent&short_desc_type=allwordssubstr&v6=intermittent&f5=component&o6=substring&f1=classification&f8=status_whiteboard&short_desc=Intermittent&f10=CP&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f3=OP&v9=intermittent&o9=substring&v7=intermittent&o4=substring&v4=intermittent&o7=substring&f7=short_desc&f4=product&list_id=17181051&f9=cf_crash_signature

This was discussed at a previous team meeting and the theory put forward that some of the tests are exhausting system resources and causing other tests that happen to be running in parallel to fail.

One possibility for dealing with this is to flag these tests so that they are not run in parallel with other tests. However not running these tests in parallel may significantly increase test time.

The tests in question seem to be the wasm/memory64 tests.

Assignee: nobody → bvisness
Blocks: sm-testing
Severity: -- → S3
Priority: -- → P1
Attachment #9423626 - Attachment description: WIP: Bug 1914577: Add a `sequential` directive to js tests. → Bug 1914577: Add a `sequential` directive to js tests. r=jandem
Attachment #9423627 - Attachment description: WIP: Bug 1914577: Mark most wasm memory64 tests as sequential. → Bug 1914577: Mark most wasm memory64 tests as sequential. r=jseward

"Heavy" tests will never be run in parallel. Useful for tests that
consume large amounts of system resources.

Attachment #9423626 - Attachment is obsolete: true
Attachment #9423627 - Attachment is obsolete: true
Attachment #9425154 - Attachment description: WIP: Bug 1914577: Add "heavy" flag to jit-test harness. → Bug 1914577: Add "heavy" flag to jit-test harness. r=sfink
Attachment #9425338 - Attachment description: WIP: Bug 1914577: Mark most wasm memory64 tests as heavy. → Bug 1914577: Mark most wasm memory64 tests as heavy. r=yury
Pushed by bvisness@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/fe1d748f2f5d Add "heavy" flag to jit-test harness. r=sfink https://hg.mozilla.org/integration/autoland/rev/8fe641746ac4 Mark most wasm memory64 tests as heavy. r=yury
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
Regressions: 1932131
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: