Bug 235995
Summary: | REGRESSION(r288914): [ BigSur+ arm64 Release ] Bots are constantly exiting testing early with 500+ layout-test failures | ||
---|---|---|---|
Product: | WebKit | Reporter: | Robert Jenner <jenner> |
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | ap, bfulgham, simon.fraser, webkit-bot-watchers-bugzilla, webkit-bug-importer, zalan |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=235937 |
Robert Jenner
BigSur and Monterey Apple Silicon Release bots are constantly exiting testing early with 500+ layout-test failures.
You can see this on the following four queues:
https://build.webkit.org/#/builders/Apple-Monterey-Release-AppleSilicon-WK2-Tests?numbuilds=50
https://build.webkit.org/#/builders/Apple-Monterey-Release-AppleSilicon-WK1-Tests?numbuilds=50
https://build.webkit.org/#/builders/Apple-BigSur-Release-AppleSilicon-WK2-Tests?numbuilds=50
https://build.webkit.org/#/builders/Apple-BigSur-Release-AppleSilicon-WK1-Tests?numbuilds=50
Here is a list of the test failures occurring:
https://build.webkit.org/results/Apple-Monterey-Release-AppleSilicon-WK2-Tests/r288925%20(1332)/results.html
They all appear to be tests that deal with layout and rendering, and they all have diffs that are just slightly off.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/88358964>
Robert Jenner
I was able to reproduce the failures using the following test at Monterey Release ToT:
run-webkit-tests --no-build --no-show-results --no-new-test-results --clobber-old-results --exit-after-n-crashes-or-timeouts 50 --exit-after-n-failures 500 --release --debug-rwt-logging --no-retry-failures
I was able to reproduce the failures at r288914, but not at r288913. So it appears that r288914 is what broke testing on Apple Silicon.
Alexey Proskuryakov
*** This bug has been marked as a duplicate of bug 235998 ***