Greg, are you around still?
Just let me double check the regression range before we back out anything.
Hmm...the patch passed tests on Gaia Try so I landed it, and the most strange thing is from the code I don't have any clue about why it would cause the error. However, if this is a regression, we can back it out and I would spend time on it.
This hasn't shown up on any desktopb2g tests, it's only on device. Our device testing is getting it intermittently so I need a bit more time to track down a more accurate regression range.
Dave generated a regression range from on-device automation: http://hg.mozilla.org/integration/b2g-inbound/pushloghtml?fromchange=0b934bed627f&tochange=63c5f891c11a I reverted: https://github.com/mozilla-b2g/gaia/tree/e13cc05b6d615664d769e55b60754480848d076b and ran the tests while observing the logcat. The error is only present with the above commit included.
(In reply to Zac C (:zac) from comment #5) > I reverted: > https://github.com/mozilla-b2g/gaia/tree/ > e13cc05b6d615664d769e55b60754480848d076b Diff link: https://github.com/mozilla-b2g/gaia/commit/e13cc05b6d615664d769e55b60754480848d076b
edmorley, can we back that out on account of the test failures?
Don't we need to open the original bug in case of backouts? Is this one fixed now due to the backout?
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(In reply to Kevin Grandon :kgrandon from comment #9) > Don't we need to open the original bug in case of backouts? Is this one > fixed now due to the backout? Yeah sorry completely forgot.
I just noticed this is affecting v2.0 branch in the same way (I only just checked the results then)., Ed can you do the same on v2.0? Thanks
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Kevin cherrypicked the revert already (thank you :-)): https://github.com/mozilla-b2g/gaia/commit/a5283446aab3d4e730973ed3fc1de69b7e874c08
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago → 4 years ago
Resolution: --- → FIXED
Everything should be resolved now. Please let me know if you run into this issue again, and include the stack. Thanks!
So far I have not seen this issue come up in some of the builds that were failing. Thanks for landing this so quickly. I'll monitor it periodically over the weekend.
You need to log in before you can comment on or make changes to this bug.