Bug 1713908 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Thanks for following-up! Short answer, if we can't reproduce anymore, let's use this bug to remove the annotation.

Longer answer: 
Enabling new platforms is messy. In this case there were dozens of failures, pre-existing intermittents and the patch was created over the span of weeks. To get coverage on these platforms ASAP, I was also erring on the side of over-disabling when in doubt. So it's possible I either made a mistake, the problem was fixed between now and when I first annotated the manifest, or the test is intermittent and just happened to not fail on these three tasks. I added a few more retriggers to verify.

This bug was filed via script (first time being used), so the process is still being ironed out. I'll adjust the template in the script to make it more clear that A) this is automated, and B) what to do if the failure is not reproducible.

Thanks for understanding!
Thanks for following-up! Short answer: If we can't reproduce anymore, let's use this bug to remove the annotation.

Longer answer: 
Enabling new platforms is messy. In this case there were dozens of failures, pre-existing intermittents and the patch was created over the span of weeks. To get coverage on these platforms ASAP, I was also erring on the side of over-disabling when in doubt. So it's possible I either made a mistake, the problem was fixed between now and when I first annotated the manifest, or the test is intermittent and just happened to not fail on these three tasks. I added a few more retriggers to verify.

This bug was filed via script (first time being used), so the process is still being ironed out. I'll adjust the template in the script to make it more clear that A) this is automated, and B) what to do if the failure is not reproducible.

Thanks for understanding!

Back to Bug 1713908 Comment 3