Bug 230060 – [iOS14 Release iPhone] fast/shapes/shape-outside-floats/shape-outside-big-box-border-radius-001.html is a flaky crash

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: Layout and Rendering

[Eric Hutchison]

fast/shapes/shape-outside-floats/shape-outside-big-box-border-radius-001.html

is a flaky crash on iOS14 Release on iPhone.

History: https://results.webkit.org/?suite=layout-tests&test=fast%2Fshapes%2Fshape-outside-floats%2Fshape-outside-big-box-border-radius-001.html

Results: https://build.webkit.org/results/Apple-iOS-14-Simulator-Release-WK2-Tests/r282141%20(3113)/results.html

Diff: 
Crash Log: None
No crash log found for WebKitTestRunnerApp:11745.

Unable to reproduce crash using run-webkit-tests --iOS-simulator --iterations 1000 --exit-after-n-crashes-or-timeouts 1 --clobber-old-results fast/shapes/shape-outside-floats/shape-outside-big-box-border-radius-001.html.

[Radar WebKit Bug Importer]

<rdar://problem/82888111>

[Eric Hutchison]

Updated test expectations at http://trac.webkit.org/changeset/282167/webkit

[Radar WebKit Bug Importer]

<rdar://problem/82888370>

[Alexey Proskuryakov]

This is not an actual crash. Looking at this run https://build.webkit.org/#/builders/28/builds/3165/steps/11/logs/stdio, I see:

20:51:34.738 86218 worker/3 fast/shadow-dom/ios/accessory-bar-work-on-input-with-tabindex-in-shadow-tree.html passed
20:51:34.746 86218 worker/3 finished test group
...
20:51:34.835 86218 worker/3 killed pid 89631
20:51:34.836 86218 worker/3 This test marked as a crash because of a broken pipe when writing to stdin of the server process.
...
20:52:14.885 86218 worker/3 worker/3 fast/shapes/shape-outside-floats/shape-outside-big-box-border-radius-001.html crashed, (no stderr)
20:52:14.888 86218 worker/3 killing driver
20:52:14.904 86218 worker/3 fast/shapes/shape-outside-floats/shape-outside-big-box-border-radius-001.html failed:
20:52:14.904 86218 worker/3 WebKitTestRunnerApp crashed [pid=89631]

And on the machine, there isn't anything interesting in the logs, only logs about taking and releasing SystemIsActive powerd assertions.

log show --start "2021-09-10 20:51:00" --end "2021-09-10 20:55:00" | grep 89631

2021-09-10 20:51:31.594823-0700 0x3449176  Default     0x106fcfc            66     0    powerd: [powerd:assertions] Process runningboardd.86749 Created SystemIsActive "xpcservice<com.apple.WebKit.GPU([application<org.webkit.WebKitTestRunnerApp>:89631])>:8977586749-89631-2184:GPUProcess Foreground Assertion" age:00:00:00  id:51539640496 [System: PrevIdle DeclUser SysAct IntPrevDisp kDisp]
2021-09-10 20:51:34.858738-0700 0x3449176  Default     0x107012e            66     0    powerd: [powerd:assertions] Process runningboardd.86749 Released SystemIsActive "xpcservice<com.apple.WebKit.GPU([application<org.webkit.WebKitTestRunnerApp>:89631])>:8977586749-89631-2184:GPUProcess Foreground Assertion" age:00:00:03  id:51539640496 [System: PrevIdle DeclUser SysAct IntPrevDisp kDisp]
2021-09-10 20:51:34.872036-0700 0x3449176  Default     0x1070147            66     0    powerd: [powerd:assertions] Process runningboardd.86749 Released SystemIsActive "xpcservice<com.apple.WebKit.Networking([application<org.webkit.WebKitTestRunnerApp>:89631])>:8963286749-89631-2182:NetworkProcess Foreground Assertion" age:00:00:03  id:51539640495 [System: PrevIdle DeclUser SysAct IntPrevDisp kDisp]
2021-09-10 20:51:34.885897-0700 0x3449176  Default     0x1070160            66     0    powerd: [powerd:assertions] Process runningboardd.86749 Released SystemIsActive "xpcservice<com.apple.WebKit.WebContent([application<org.webkit.WebKitTestRunnerApp>:89631])>:8977286749-89631-2181:WebProcess Foreground Assertion" age:00:00:03  id:51539640494 [System: PrevIdle DeclUser SysAct IntPrevDisp kDisp]

[Alexey Proskuryakov]

Broken pipe is weird, but also not sure why it took 40 seconds between "This test marked as a crash because of a broken pipe" and "crashed".

[Simon Fraser (smfr)]

Seems like some kinds of process unresponsiveness/lack of output result in us calling something a "crash" when it's not. Would be nice to fix this.

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