Fix some startup cache invalidation issues
Categories
(Core :: XPCOM, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox115 | --- | fixed |
People
(Reporter: kmag, Assigned: kmag)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
Assignee | ||
Comment 1•3 years ago
|
||
Assignee | ||
Comment 2•3 years ago
|
||
Assignee | ||
Comment 3•3 years ago
|
||
Comment 4•3 years ago
|
||
There are some r+ patches which didn't land and no activity in this bug for 2 weeks.
:kmag, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Comment 6•3 years ago
|
||
Comment 7•3 years ago
|
||
Kris is still figuring out why it fails on automation but no luck yet.
Updated•3 years ago
|
Comment 8•3 years ago
|
||
At least one of the Marionette tests failing with these patches is test_preloader_telemetry.py. That test involves invalidating the cache, so it makes sense that it would have an effect. I found an issue with how the test deals with failure, and file bug 1757250 for that, but that won't fix the actual issue.
Comment 9•3 years ago
|
||
test_preloader_telemetry.py invalidates the cache, then restarts the browser, then waits for cache files to be created, which never happens with the patch. Restarting the browser an extra time makes the test pass. I could see how that might make sense, but I need to get my head around what exactly the invalidation logic is doing here to figure out if needing that change is expected.
Comment 10•2 years ago
|
||
Kris, is this something worth resuming that perhaps would help bug 1724336?
Comment 11•1 years ago
|
||
Comment 12•1 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/799aaf92ef59
https://hg.mozilla.org/mozilla-central/rev/5569f440c128
https://hg.mozilla.org/mozilla-central/rev/c3994fed323f
Assignee | ||
Updated•1 years ago
|
Description
•