I can't for the life of me get this to fail on my own macbook locally, having run dozens of tests. It doesn't seem likely that this test was actually causing the error, the it seems as though the problem is happening in this code:
```
add_task(async function testEnabledForValidURLs() {
await testMenuEnabledForValidURLs(AppMenu());
await testMenuEnabledForValidURLs(HelpMenu());
// it seems to be hanging here
await testMenuEnabledForValidURLs(ProtectionsPanel());
});
```
So this smells like another instance of what bit me here:
https://searchfox.org/mozilla-central/source/browser/components/reportbrokensite/test/browser/browser_report_site_issue_fallback.js#75-78
Since that is related more to the inability to test the Help menu all that reliably (requiring odd hacks), I think I'd rather disable the test here as well for now.
Bug 1952334 Comment 22 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't for the life of me get this to fail on my own macbook locally, having run dozens of tests. It seems as though the problem is happening in this code:
```
add_task(async function testEnabledForValidURLs() {
await testMenuEnabledForValidURLs(AppMenu());
await testMenuEnabledForValidURLs(HelpMenu());
// it seems to be hanging here
await testMenuEnabledForValidURLs(ProtectionsPanel());
});
```
So this smells like another instance of what bit me here:
https://searchfox.org/mozilla-central/source/browser/components/reportbrokensite/test/browser/browser_report_site_issue_fallback.js#75-78
Since that is related more to the inability to test the Help menu all that reliably (requiring odd hacks), I think I'd rather disable the test here as well for now.