NEW 172283
[GTK] Test inspector/worker/debugger-multiple-targets-pause.html is flaky
https://bugs.webkit.org/show_bug.cgi?id=172283
Summary [GTK] Test inspector/worker/debugger-multiple-targets-pause.html is flaky
Miguel Gomez
Reported 2017-05-18 03:43:57 PDT
Test inspector/worker/debugger-multiple-targets-pause.html is flaky
Attachments
Miguel Gomez
Comment 1 2017-05-18 03:46:38 PDT
The flakiness happens because the test times out sometimes.
Miguel Gomez
Comment 2 2019-05-02 07:17:21 PDT
It's flaky pass/fail/timeout now. This is the diff when it fails: --- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/inspector/worker/debugger-multiple-targets-pause-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/inspector/worker/debugger-multiple-targets-pause-actual.txt @@ -7,24 +7,31 @@ PASS: Created Worker 2 -- Running test case: Worker.Debugger.Threads.Pause +ASSERT: undefined PASS: Paused event should happen before CallFramesDidChange event. -PASS: In Paused event all other Targets should be pausing. +FAIL: In Paused event all other Targets should be pausing. + Expected: truthy + Actual: false PASS: Worker 1 should be the first to pause. PASS: All Targets should eventually pause. TARGET: Page CALL FRAME #1: workOnMainThread +TARGET: worker-debugger-thread-2.js + CALL FRAME #1: workInThread2 TARGET: worker-debugger-thread-1.js * CALL FRAME #1: foo CALL FRAME #2: workInThread1 -TARGET: worker-debugger-thread-2.js - CALL FRAME #1: workInThread2 -- Running test case: Worker.Debugger.Threads.Paused.Worker1Evaluate -PASS: Evaluated result in worker-debugger-thread-1.js should be "worker thread 1". +FAIL: Evaluated result in worker-debugger-thread-2.js should be "worker thread 1". + Expected: "worker thread 1" + Actual: "worker thread 2" -- Running test case: Worker.Debugger.Threads.Paused.Worker2Evaluate -PASS: Evaluated result in worker-debugger-thread-2.js should be "worker thread 2". +FAIL: Evaluated result in worker-debugger-thread-1.js should be "worker thread 2". + Expected: "worker thread 2" + Actual: "worker thread 1" -- Running test case: Worker.Debugger.Threads.Paused.MainEvaluate PASS: Evaluated result in Page should be "main thread". @@ -34,25 +41,27 @@ TARGET: Page CALL FRAME #1: workOnMainThread +TARGET: worker-debugger-thread-2.js TARGET: worker-debugger-thread-1.js - * CALL FRAME #1: workInThread1 -TARGET: worker-debugger-thread-2.js - CALL FRAME #1: workInThread2 + CALL FRAME #1: foo + CALL FRAME #2: workInThread1 -- Running test case: Worker.Debugger.Threads.Paused.Worker2.ResumeThread PASS: Should Receive CallFramesDidChange for Worker 2. PASS: Worker 2 should be pausing. -PASS: Should Receive CallFramesDidChange for Worker 2. -PASS: Worker 2 should be paused. - -TARGET: Page - CALL FRAME #1: workOnMainThread -TARGET: worker-debugger-thread-1.js - * CALL FRAME #1: workInThread1 -TARGET: worker-debugger-thread-2.js - CALL FRAME #1: laterWorkInThread2 +!! TIMEOUT: took longer than 10000ms -- Running test case: Worker.Debugger.Threads.Complete PASS: Received Resume event. PASS: All Targets should be unpaused. +FAIL: Should Receive CallFramesDidChange for Worker 2. + Expected: WorkerTarget instance #2 + Actual: PageTarget instance #1 +FAIL: Worker 2 should be paused. + Expected: truthy + Actual: false +TARGET: Page +TARGET: worker-debugger-thread-2.js +TARGET: worker-debugger-thread-1.js +
Note You need to log in before you can comment on or make changes to this bug.