Closed Bug 1564810 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 17564 - Release the mozlog lock when starting test runner processes

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox70 fixed)

RESOLVED FIXED
mozilla70
Tracking Status
firefox70 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 17564 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/17564
Details from upstream follow.

Josh Matthews <josh@joshmatthews.net> wrote:

Release the mozlog lock when starting test runner processes

This is a follow up to #17433 which addresses a deadlock observed in Servo's CI in a PR that introduces the first fuzzy reftest results. The thread responsible for interpreting the pixels in the images deadlocks when initializing PIL which makes logging calls. Since this is in a separate process from the main wptrunner overseer, it seems logical that ensuring the mutex is released after spawning the test runner processes would make the deadlock disappear. I was able to successfully run the reftest in question many times in a row without deadlocking after making this change, whereas previously I would hit it on the first or second try.

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Type: -- → task
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/81933c196142 [wpt PR 17564] - Release the mozlog lock when starting test runner processes, a=testonly
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.