Bugzilla

One idea for a way forward here... Maybe it'd be worth activating the "full log" for mochitest-a11y-* tests (temporarily at least), to hopefully gather some more data?   (That might even make the test-failure line show up in the log, which would be a clue about what's going on and why it's not showing up in the concise log.)

Essentially, it might be worth trying to effectively call `SimpleTest.requestCompleteLog()`[1] for every single test in this test-suite.  (But probably not *actually* do that -- just change the default behavior for mochitest-a11y-* or something like that, temporarily.)

(I don't know precisely how to do that, but I'm pretty sure it should be possible.)

[1] https://firefox-source-docs.mozilla.org/testing/mochitest-plain/faq.html#how-can-i-get-the-full-log-output-for-my-test-in-automation-for-debugging

One idea for a way forward here... Maybe it'd be worth activating the "full log" for mochitest-a11y-* tests (temporarily at least), to hopefully gather some more data?   (That might even make the test-failure line show up in the log, which would be a clue about what's going on and why it's not showing up in the current "more concise" logs.)

In other words: it might be worth trying to effectively call `SimpleTest.requestCompleteLog()`[1] for every single test in this test-suite.  (But probably not *actually* do that -- just change the default behavior for mochitest-a11y-* or something like that, temporarily.)

(I don't know precisely how to do that, but I'm pretty sure it should be possible.)

[1] https://firefox-source-docs.mozilla.org/testing/mochitest-plain/faq.html#how-can-i-get-the-full-log-output-for-my-test-in-automation-for-debugging