| Summary: | REGRESSION (251741@main-251739@main?): [ iOS ] TestWebKitAPI.AutocorrectionTests.AutocorrectionContextBeforeAndAfterEditing is a flaky failure | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Karl Rackler <rackler> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | ap, honamluxurychef, ryanhaddad, webkit-bot-watchers-bugzilla, webkit-bug-importer, wenson_hsieh |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=241890 | ||
|
Description
Karl Rackler
2022-06-29 12:53:38 PDT
I have disabled this test while this issue is investigated. Test gardening commit 251961@main (9aa946bf2540): <https://commits.webkit.org/251961@main> Reviewed commits have been landed. Closing PR #1912 and removing active labels. The test failure is referencing contextAfterInsertingText and contextAfterSelecting from 246659@main. The flakiness dashboard shows a clear change from consistently passing to flaky failure first appearing on the dashboard at 251749@main. Reproduction steps further reduced the range(251741@main-251739@main), but it is unclear what in this range may have caused this. (In reply to Karl Rackler from comment #4) > The test failure is referencing contextAfterInsertingText and > contextAfterSelecting from 246659@main. > > The flakiness dashboard shows a clear change from consistently passing to > flaky failure first appearing on the dashboard at 251749@main. > > Reproduction steps further reduced the range(251741@main-251739@main), but > it is unclear what in this range may have caused this. Yeah, neither of the commits in that range remotely seem like they could've caused these test failures. Were there any interesting configuration changes might've affected the bots at around the same time? (i.e. upgrading to a different version, or using new simulator device models, etc.) (In reply to Wenson Hsieh from comment #5) > Were there any interesting configuration changes might've affected the bots > at around the same time? (i.e. upgrading to a different version, or using > new simulator device models, etc.) We have not made any changes in this area recently, we're also seeing this failure on internal bots in roughly the same regression range http://commits.webkit.org/compare/251744@main...251736@main Not sure what happened with my URL in comment 6, it should be showing a range of 251744@main - 251736@main http://commits.webkit.org/compare/251744@main...251736@main |