Bug 188056 - [WPE] workers/wasm-hashset-many.html is flaky
Summary: [WPE] workers/wasm-hashset-many.html is flaky
Status: RESOLVED DUPLICATE of bug 177940
Alias: None
Product: WebKit
Classification: Unclassified
Component: WPE WebKit (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-26 07:47 PDT by Miguel Gomez
Modified: 2020-12-14 22:35 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Miguel Gomez 2018-07-26 07:47:44 PDT 
workers/wasm-hashset-many.html [ Timeout Pass ]

The test times out on the first run around 50% of the time. There's no stderr or extra information about why.
Comment 1 Lauro Moura 2020-03-06 17:57:33 PST 
Flaky crashing since between r253137 and r253142

r253137                       TIMEOUT (Expected: PASS TIMEOUT)
r253142                       CRASH (Expected: PASS TIMEOUT)
Comment 2 Lauro Moura 2020-03-06 18:31:05 PST 
Sample stack from crash on https://build.webkit.org/results/WPE%20Linux%2064-bit%20Release%20(Tests)/r258024%20(17196)/workers/wasm-hashset-many-crash-log.txt

Thread 1 (Thread 0x7f61770c2e40 (LWP 6167)):
#0  0x00007f618181ca7d in JSC::Wasm::operationWasmTriggerOSREntryNow(JSC::Probe::Context&) () from /home/buildbot/wpe/wpe-linux-64-release/build/WebKitBuild/Release/lib/libWPEWebKit-1.0.so.3
#1  0x00007f6180db838d in JSC::Probe::executeProbe(JSC::Probe::State*) () from /home/buildbot/wpe/wpe-linux-64-release/build/WebKitBuild/Release/lib/libWPEWebKit-1.0.so.3
#2  0x00007f6180db6c32 in ctiMasmProbeTrampoline () from /home/buildbot/wpe/wpe-linux-64-release/build/WebKitBuild/Release/lib/libWPEWebKit-1.0.so.3
#3  0x00007f61368b1fed in ?? ()
#4  0x00007f6134de6000 in ?? ()
#5  0x00007f54e6028b60 in ?? ()
#6  0x0000000000501b60 in ?? ()
#7  0x00007f60d132bd80 in ?? ()
#8  0x0000000000000000 in ?? ()
Comment 3 Diego Pino 2020-12-14 22:35:15 PST 

*** This bug has been marked as a duplicate of bug 177940 ***