Bug 206523 – http/tests/cookies/same-site/fetch-in-same-origin-page.html is flaky crash on iOS

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: Tools / Tests

[Aakash Jain]

http/tests/cookies/same-site/fetch-in-same-origin-page.html is flaky crash on iOS.

For e.g. in https://ews-build.webkit.org/#/builders/24/builds/8899 this test crashed in layout-tests step, while in subsequent re-run-layout-tests step it passed.

https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Fcookies%2Fsame-site%2Ffetch-in-same-origin-page.html also shows occasional crash.

e.g.:
https://build.webkit.org/builders/Apple%20iOS%2013%20Simulator%20Release%20WK2%20%28Tests%29/builds/2081
https://build.webkit.org/builders/Apple%20iOS%2013%20Simulator%20Release%20WK2%20%28Tests%29/builds/2044
https://build.webkit.org/builders/Apple%20iOS%2013%20Simulator%20Release%20WK2%20%28Tests%29/builds/2031
https://build.webkit.org/builders/Apple%20iOS%2013%20Simulator%20Release%20WK2%20%28Tests%29/builds/2021

[Aakash Jain]

https://build.webkit.org/builders/Apple%20iOS%2013%20Simulator%20Release%20WK2%20%28Tests%29/builds/2021

stdio:
10:44:09.607 98852 ServiceWorkerProcess crash, pid = 3466
10:44:09.772 98852 This test marked as a crash because of no data while reading stdout for the server process.
10:44:09.772 98852 This test marked as a crash because of no data while reading stdout for the server process.
10:44:59.833 98852 worker/0 http/tests/cookies/same-site/fetch-in-same-origin-page.html crashed, (no stderr)
10:44:59.836 97039 [22041/48343] http/tests/cookies/same-site/fetch-in-same-origin-page.html failed unexpectedly (ServiceWorkerProcess crashed [pid=3466])
10:44:59.834 98852 worker/0 killing driver
10:44:59.893 98852 worker/0 http/tests/cookies/same-site/fetch-in-same-origin-page.html failed:
10:44:59.893 98852 worker/0  ServiceWorkerProcess crashed [pid=3466]

[Alexey Proskuryakov]

Another ServiceWorkerProcess crash. Youenn, could you please dupe to the master bug?

[youenn fablet]

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