I'm confused, I think the regressing bug is misattributed. Bug 2026000 hit autoland at 25 Mar 2026 13:56:31 +0000. The failing test is in an autoland job from 25 Mar 2026 08:58:24 +0000, 5 hours earlier. Bug 2026000 is an Android audio backend change, but the failing test doesn't use audio AFAICT. We have had lots of unrelated-to-audio tests failing on the Android emulator runners due to audio bugs, however. Bug 2025563 hit autoland at 24 Mar 2026 08:21:50 +0000, that was intended to fix those random timeouts, but may have caused some to shift to other bugs. I don't have any evidence that this test timeout is related to bug 2025563 or audio yet, but I'll check.
Bug 2026147 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.
I'm confused, I think the regressing bug is misattributed. Bug 2026000 hit autoland at 25 Mar 2026 13:56:31 +0000. The failing test is in an autoland job from 25 Mar 2026 08:58:24 +0000, 5 hours earlier. Bug 2026000 is an Android audio backend change, but the failing test doesn't use audio AFAICT. We have had lots of unrelated-to-audio tests failing on the Android emulator runners due to audio bugs, however. Bug 2025563 hit autoland at 24 Mar 2026 08:21:50 +0000, that was intended to fix those random timeouts, but may have caused some to shift to other bugs - OTOH if this test timeout is high frequency, I'd expect it to show up sooner and be more clearly linked to that bug landed. I don't have any evidence that this test timeout is related to bug 2025563 or audio yet, but I'll check.