![]() ![]() There’s not much we can do here except adjust our idle times, which isn’t the ideal solution. ![]() The Azure workers, in particular, take a long time to spin up and down, and these processes block spinning other pools up or down. There is a single process that goes through worker pool by worker pool to spin workers up and down on demand. Second, as of 2022.01.26, we have had a number of issues with worker-manager. Image bump that caused the Mercurial upgrade to beta, release and esr branches. ![]() When I run hg -version on the server is shows version 1.8.3 instead of 2.6 I have rebooted and in the Workbench UI it shows the correct ver. To mitigate this, consider backporting the We just upgraded Team City and Mecurial on our server. Will have more cache misses, resulting in longer runtimes which could impact The downside to doing this is that tasks on older branches with less traffic The name (e.g incrementing v2 -> v3), will ensure workers don’t re-use the For example, the Gecko decision tasks use this cache name. The solution is to increment the cache identifier associated with the checkoutĬache. Mozilla-release, the latter task might fail if it is using an older Mozilla-central, clones the repo, and then claims a task on Since workers have a sharedĬheckout cache between tasks, if a worker first claims a task on e.g, Incompatible with older versions of Mercurial. This happens because repos cloned via newer versions of Mercurial are often Troubleshooting Expirations NotificationsĪdding a keyword to mochitest and xpcshell manifestsĪdding a keyword to reftest style manifestsĪbort: repository requires features unknown to this Mercurial: revlog-compression-zstd! How to rotate the Firefox Release signing GPG Key Testing and Customizing Release Promotion actionsĬreate a new release key to sign a new apk product Turning on Firefox tests for a new configuration Off-Cycle Partner Repacks and Funnelcakes How to automate nightly Google Play deployments Scriptworker-scripts Wiki (mac signing procedures) ![]()
0 Comments
Leave a Reply. |