(In reply to Intermittent Failures Robot from comment #140) > This test has failed more than 150 times in the last 21 days. It should be disabled until it can be fixed. Fortunately this is getting much better, per below. > 21 failures were associated with this bug in the last 7 days. > [...] > ## Repository breakdown: > * mozilla-release: 7 > * mozilla-beta: 14 Nice, -- only beta/release were affected last week. No failures on mozilla-central/autoland. So presumably the patch in comment 138 fixed things here. Today is merge day, so beta should be good as of today. But release will still be affected for the next 4 weeks (until our next merge day). If the fix were a test-change, we could trivially uplift it to release since there's no user impact -- but that's not the case here. The fix here was an actual code-change. So probably not the sort of thing we'd want to just uplift directly to the release branch mid-cycle. So: I think that means this test is doomed to keep failing on release (but nowhere else) for the next 4 weeks. If the rate is too high, we could disable the test on release, but assuming trends continue with 0-7 failures per week on release, this should hopefully be minimally-painful to live with for the time being.
Bug 1784938 Comment 141 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 Intermittent Failures Robot from comment #140) > This test has failed more than 150 times in the last 21 days. It should be disabled until it can be fixed. Fortunately this is getting much better, per below. > 21 failures were associated with this bug in the last 7 days. > [...] > ## Repository breakdown: > * mozilla-release: 7 > * mozilla-beta: 14 Nice -- only beta/release were affected last week. No failures on mozilla-central/autoland. So presumably the patch in comment 138 fixed things here. Today is merge day, so beta should be good as of today. But release will still be affected for the next 4 weeks (until our next merge day). If the fix were a test-change, we could trivially uplift it to release since there's no user impact -- but that's not the case here. The fix here was an actual code-change. So probably not the sort of thing we'd want to just uplift directly to the release branch mid-cycle. So: I think that means this test is doomed to keep failing on release (but nowhere else) for the next 4 weeks. If the rate is too high, we could disable the test on release, but assuming trends continue with 0-7 failures per week on release, this should hopefully be minimally-painful to live with for the time being.
(In reply to Intermittent Failures Robot from comment #140) > This test has failed more than 150 times in the last 21 days. It should be disabled until it can be fixed. Fortunately this is getting much better, per below. > 21 failures were associated with this bug in the last 7 days. > [...] > ## Repository breakdown: > * mozilla-release: 7 > * mozilla-beta: 14 Nice -- only beta/release were affected last week. No failures on mozilla-central/autoland. So presumably the patch in comment 138 fixed things here. Today is merge day, so beta should start being "good" as of today, too. But release will still be affected for the next 4 weeks (until our next merge day). If the fix were a test-change, we could trivially uplift it to release since there's no user impact -- but that's not the case here. The fix here was an actual code-change. So probably not the sort of thing we'd want to just uplift directly to the release branch mid-cycle. So: I think that means this test is doomed to keep failing on release (but nowhere else) for the next 4 weeks. If the rate is too high, we could disable the test on release, but assuming trends continue with 0-7 failures per week on release, this should hopefully be minimally-painful to live with for the time being.