test_reset_glean takes an awful long time if there are a lot of pending pings on disk
Categories
(Data Platform and Tools :: Glean: SDK, defect, P3)
Tracking
(Not tracked)
People
(Reporter: chutten, Unassigned)
References
Details
If there's a lot of pending pings on disk (say, a full complement of 250), then when we call test_reset_glean it can cause our tests to time out.
I'm not 100% sure on the mechanism here. Maybe it only takes so long if we're also already throttled. Maybe we're waiting somewhere other than inside uploader_shutdown (though that's the obvious place I'd check first). Maybe it's only a problem if there's something specific to newtab's mochitest setup (since the reliable STR has so far been 1) Land very chatty "about-welcome" and "as-router" pings, 2) Run the entire browser/components/newtab/tests/browser suite (optionally with --timeout 15 (or lower) if you have a fast machine) 3) Check out the timeouts on browser_newtab_ping.js )
|
||
Updated•1 year ago
|
|
Reporter | |
Comment 1•1 year ago
|
||
Dropping as it's no longer as immediately an issue. Can be reprioritized later or picked out of the backlog by someone feeling enterprising.
Description
•