I can reproduce this locally, though only if I run the entire manifest (`toolkit/mozapps/extensions/xpcshell/xpcshell.ini`), which makes it really difficult to get any meaningful debug output for the specific test that's failing. The test is passing, and reaches the end of the test task cleanly, but somehow fails to exit and hangs on shutdown. I expect it's nothing to do with this specific test, but somehow remote settings and/or its indexeddb access does not play nicely with the xpcshell test infrastructure these tests use. Any clues as to where I should start debugging? We're hoping to ship this with 72, and this is a bit of a nasty surprise and the only blocker to the otherwise straightforward pref flip.
Bug 1594521 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I can reproduce this locally, though only if I run the entire manifest (`toolkit/mozapps/extensions/test/xpcshell/xpcshell.ini`), which makes it really difficult to get any meaningful debug output for the specific test that's failing. The test is passing, and reaches the end of the test task cleanly, but somehow fails to exit and hangs on shutdown. I expect it's nothing to do with this specific test, but somehow remote settings and/or its indexeddb access does not play nicely with the xpcshell test infrastructure these tests use. Any clues as to where I should start debugging? We're hoping to ship this with 72, and this is a bit of a nasty surprise and the only blocker to the otherwise straightforward pref flip.