Closed Bug 1631991 Opened 1 year ago Closed 1 year ago

Startupcache gtest StartupWriteRead sits and waits 60 seconds for the write to happen

Categories

(Core :: XPCOM, defect)

defect

Tracking

()

RESOLVED FIXED
mozilla79
Tracking Status
firefox79 --- fixed

People

(Reporter: Gijs, Assigned: Gijs)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

[task 2020-04-21T23:13:34.538Z] 23:13:34 INFO - TEST-PASS | TestStartupCache.StartupWriteRead | test completed (time: 61797ms)

On Android, this is 1 minute out of the 5.5 it takes to actually run all of gtests, on a 7-minute job

On desktop, it's less pronounced, 1 minute out of jobs that take anywhere between 14 and 22 minutes - but still, that's 5% of the job runtime.

On an m-c push we run more than a dozen of these jobs (so we lose, say, 15 minutes per push), so between that and autoland fixing this to be less extreme probably reduces test machine runtime by a few hours every day?

We could use a static pref to lower the write interval, or just check for the gtest constructor existing and lowering it based on that.

Assignee: nobody → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Pushed by gijskruitbosch@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/a60ab910b268
stop wasting minutes of infra time waiting for the startup cache in gtests, r=dthayer
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
You need to log in before you can comment on or make changes to this bug.