Reasoning: 1) It's not a regression [oops, that keyword was present for some reason -- removing]; just a new test from upstream that happens to occasionally fail. 2) It's unknown at this point whether it's a test bug or a Firefox bug 3) I tried to reproduce locally, on Monday, & was unable to do so (using a few runs of `./mach wpt --verify` which uses chaos mode) 4) Given the other reasons, I don't think anyone will be able to jump on fixing this right away (nor does it rise to the priority of drop-other-things-to-investigate)
Bug 1540829 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Reasoning: 1) It's not a regression [oops, that keyword was present for some reason -- removing]; just a new test from upstream that happens to occasionally fail. 2) It's unknown at this point whether it's a test bug or a Firefox bug 3) I tried to reproduce locally, on Monday, & was unable to do so (using a few runs of `./mach wpt --verify` which uses chaos mode; not sure what I can do beyond that to try to make it happen in a locally debuggable way) 4) Given the other reasons, I don't think anyone will be able to jump on fixing this right away (nor does it rise to the priority of drop-other-things-to-investigate)
Reasoning: 1) It's not a regression [oops, that keyword was present for some reason -- removing]; just a new test from upstream that happens to occasionally fail. 2) It's unknown at this point whether it's a test bug or a Firefox bug 3) I tried to reproduce locally, on Monday, & was unable to do so (using a few runs of `./mach wpt --verify` which uses chaos mode; not sure what I can do beyond that to try to make it happen in a locally debuggable way) 4) Given the above, I don't think anyone will be able to jump on fixing this right away (nor does it rise to the priority of drop-other-things-to-investigate)
Reasoning: 1) It's not a regression [oops, that keyword was present for some reason -- removing]; just a new test from upstream that happens to occasionally fail. 2) It's unknown at this point whether it's a test bug or a Firefox bug 3) I tried to reproduce locally, on Monday, & was unable to do so (using a few runs of `./mach wpt --verify` which uses chaos mode; not sure what I can do beyond that to try to make it happen in a locally debuggable way) 4) Given the above, I don't think anyone will be able to jump on fixing this right away (nor does it rise to the priority of drop-other-things-to-investigate, beyond the quick attempt that I tried to do in (3))
Reasoning: 1) It's not a regression [oops, that keyword was present for some reason -- removing]; just a new test from upstream that happens to occasionally fail. 2) It's unknown at this point whether it's a test bug or a Firefox bug 3) I tried to reproduce locally, on Monday, & was unable to do so (using a few runs of `./mach wpt --verify` which uses chaos mode; not sure what I can do beyond that to try to make it happen in a locally debuggable way) 4) Given the above, I don't think anyone will be able to jump on fixing this right away (nor does it rise to the priority of drop-other-things-to-investigate, beyond the time-boxed attempt that I tried to do in (3))