(In reply to Dan Robertson (:dlrobertson) from comment #30) > (In reply to Cristian Tuns from comment #29) > > The bugs are different but might have the same regression Bug (Bug 1782921) that's why I mentioned the tier 2 bug. > > I may be missing something, but the regression bug (bug 1782921) landed just a few hours ago, well after `test_group_hittest-2.html` became perma (bug 1776972 comment 23). Comment 23 is when this test was disabled on some platforms, because its intermittent failure rate was too high (but not close to "perma"). The sharp increase in failure rate (going "perma") is more recent and does coincide with bug 1782921 landing. Basically, it's the same issue as bug 1785026, it's just that for some reason, some failures contain "unknown test url" instead of "test_group_hittest-2.html" in the failure line and so get associated with bug 1785026 rather than this one.
Bug 1776972 Comment 32 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Dan Robertson (:dlrobertson) from comment #30) > (In reply to Cristian Tuns from comment #29) > > The bugs are different but might have the same regression Bug (Bug 1782921) that's why I mentioned the tier 2 bug. > > I may be missing something, but the regression bug (bug 1782921) landed just a few hours ago, well after `test_group_hittest-2.html` became perma (bug 1776972 comment 23). Comment 23 is when this test was disabled on some platforms, because its intermittent failure rate was too high (but not close to "perma"). The sharp increase in failure rate on remaining platforms (going "perma") is more recent and does coincide with bug 1782921 landing. Basically, it's the same issue as bug 1785026, it's just that for some reason, some failures contain "unknown test url" instead of "test_group_hittest-2.html" in the failure line and so get associated with bug 1785026 rather than this one.