New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Safari builds fail on web-share/share-sharePromise-internal-slot.https.html #18995
Comments
The test where everything falls apart is https://github.com/web-platform-tests/wpt/blob/master/web-share/share-sharePromise-internal-slot.https.html, which uses |
Interestingly, this test also trips a DCHECK on Chrome, which I'm not sure whether is a coincidence: https://crbug.com/1002514 |
This is probably also the cause for failure for Safari stable: (Logs too big to view online, and don't know how to open huge textfiles in ChromeOS.) |
#19003 merged, these two builds will tell if that was enough to recover: |
https://wpt.fyi/results/web-share/share-sharePromise-internal-slot.https.html?sha=857ac64cb1&label=pr_head (for #19004) showed that running just that test doesn't fail. So probably there's bad state that this test runs into, caused by some previous test. |
…full Safari runs, a=testonly Automatic update from web-platform-tests Exclude problematic web-share test from full Safari runs (#19003) Workaround for web-platform-tests/wpt#18995. -- wpt-commits: e2498db8b0ffa8175fc10d32f3aa76783430af98 wpt-pr: 19003
…full Safari runs, a=testonly Automatic update from web-platform-tests Exclude problematic web-share test from full Safari runs (#19003) Workaround for web-platform-tests/wpt#18995. -- wpt-commits: e2498db8b0ffa8175fc10d32f3aa76783430af98 wpt-pr: 19003
…full Safari runs, a=testonly Automatic update from web-platform-tests Exclude problematic web-share test from full Safari runs (#19003) Workaround for web-platform-tests/wpt#18995. -- wpt-commits: e2498db8b0ffa8175fc10d32f3aa76783430af98 wpt-pr: 19003 UltraBlame original commit: 152da801027cad67d33763e59c5d53b45104f405
…full Safari runs, a=testonly Automatic update from web-platform-tests Exclude problematic web-share test from full Safari runs (#19003) Workaround for web-platform-tests/wpt#18995. -- wpt-commits: e2498db8b0ffa8175fc10d32f3aa76783430af98 wpt-pr: 19003 UltraBlame original commit: 152da801027cad67d33763e59c5d53b45104f405
…full Safari runs, a=testonly Automatic update from web-platform-tests Exclude problematic web-share test from full Safari runs (#19003) Workaround for web-platform-tests/wpt#18995. -- wpt-commits: e2498db8b0ffa8175fc10d32f3aa76783430af98 wpt-pr: 19003 UltraBlame original commit: 152da801027cad67d33763e59c5d53b45104f405
This is happening again in #20878, need to put back the |
This is https://github.com/web-platform-tests/wpt/pull/2088820863 with workaround for #18995 and #20887.
… to 97", a=testonly Automatic update from web-platform-tests Reland "Update Safari Technology Preview to 97" (#20888) This is https://github.com/web-platform-tests/wpt/pull/2088820863 with workaround for web-platform-tests/wpt#18995 and web-platform-tests/wpt#20887. -- wpt-commits: ed3830ef10dd4cfa81dcbc7090b9a6b86a39ba64 wpt-pr: 20888
… to 97", a=testonly Automatic update from web-platform-tests Reland "Update Safari Technology Preview to 97" (#20888) This is https://github.com/web-platform-tests/wpt/pull/2088820863 with workaround for web-platform-tests/wpt#18995 and web-platform-tests/wpt#20887. -- wpt-commits: ed3830ef10dd4cfa81dcbc7090b9a6b86a39ba64 wpt-pr: 20888
Similar to the other issue I commented on today, it's not clear to me we should be tracking this. The bug here is that we can't handle Safari crashing during runs - the actual testing crashing is a WebKit bug to be filed, surely? The real issue here is #19620 (which tracks handling Safari crashing). |
Yes, given a WebKit bug we could link to that instead and close this. |
Closing this as #27427 has meant we don't need to maintain a blocklist of tests; the rest of the issue here is a safaridriver one (probably rdar://74197601). |
STP on Azure Pipelines has been failing job 2 recently:
These are not the same failure mode as #18669, although I spotted some more of that too.
https://gist.github.com/foolip/d1cb47b31c7c50d859d4bb7f1ffa4e71 is the end of the logs for the first listed build, and the other two are similar.
It started happening right after #18967 was landed, so this is probably a persistent failure that won't go away, and thus urgent.
The text was updated successfully, but these errors were encountered: