Windows tasks are often slow to start in the NSS CI
Categories
(NSS :: Build, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: beurdouche, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [nss-ci])
For some reason Windows tasks are starting quite slowly, much more than Linux or MacOS tasks for some reasons.
Having all platform "Build" tasks run as early as possible would be great.
|
Reporter | |
Comment 1•1 year ago
|
||
As an example, here, after 17 mins the build task still hasn't started.
https://treeherder.mozilla.org/jobs?repo=nss-try&fromchange=76e2c6e7fae187c6dc6658e55e3ec468aac80f6c&selectedTaskRun=uh1pkFjBRYyv7JtBCHKE0g.0
|
|
Reporter | |
Comment 2•1 year ago
|
||
38 mins and still nothing...
I also noticed that in that run one of the MacOS tasks was slow to start as well (32 mins)...
IMO, the Build tasks should start immediately after the Decision tasks, so there is some problem in the scheduling.
|
|
Reporter | |
Updated•1 year ago
|
|
||
Comment 3•1 year ago
|
||
Let's not confuse different issues please.
|
||
Comment 4•1 year ago
|
||
For Windows, the main delay is when there are no existing workers. Taskcluster can take about 30 minutes to begin provisioning new VMs in Azure, and with how provisioning works in Azure, individual pieces are provisioned. More or less because of the functionality available through the Azure API, we can see a delay of 30+ minutes for new VMs. However, once workers are in a pool, the delay between tasks should be less than 2 minutes.
Side note: we should open an additional bug for the Macs. We may need to review the current pool capacity.
|
|
||
Comment 5•1 year ago
|
||
For mac this is currently expected as there's a single worker in the pool.
Description
•