Bug 1880677 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Isn't this the same failure as bug 1775847? The file was just moved in bug 1877196, but it looks like the same timeout failure as before the move. I think the reason it's hanging for so long is the problem I described in bug 1872874 and in [this thread](https://mozilla.slack.com/archives/C04TYAPB9U7/p1704250460975889), and it might be due to bug 1833453. I think I fixed this failure in [D197559](https://phabricator.services.mozilla.com/D197559) through the judicious use of `Services.fog.testResetFOG`, but I didn't land that patch for unrelated reasons.
Isn't this the same failure as bug 1775847? The file was just moved in bug 1877196, but it looks like the same timeout failure as before the move. I think the reason it's hanging for so long is the problem I described in bug 1872874 and in [this thread](https://mozilla.slack.com/archives/C04TYAPB9U7/p1704250460975889), and it might be due to bug 1833453. The issue seems to be that if you don't call `Services.fog.testResetFOG` after every test, something seems to accumulate, and then when you finally do call it, it hangs for a really long time. But if you "distribute" it between all the subtasks, then each one executes very quickly, so the test does not time out. I think I fixed this particular test failure in [D197559](https://phabricator.services.mozilla.com/D197559) through the judicious use of `Services.fog.testResetFOG`, but I didn't land that patch for unrelated reasons.
Isn't this the same failure as bug 1775847? The file was just moved in bug 1877196, but it looks like the same timeout failure as before the move. I think the reason it's hanging for so long is the problem I described in bug 1872874 and in [this thread](https://mozilla.slack.com/archives/C04TYAPB9U7/p1704250460975889), and it might be due to bug 1833453. The issue seems to be that if you don't call `Services.fog.testResetFOG` after every test, something seems to accumulate, and then when you finally do call it, it hangs for a really long time. But if you "distribute" it between all the subtasks, then each one executes very quickly, so the test does not time out. I think I fixed this particular test failure in [D197559](https://phabricator.services.mozilla.com/D197559) through the judicious use of `Services.fog.testResetFOG`, but I didn't land that patch for unrelated reasons.

I submitted a new patch, just to fix this test, at [D202078](https://phabricator.services.mozilla.com/D202078). I'll close this bug after it lands.

Back to Bug 1880677 Comment 2