Open jckeme-rs opened 2 years ago
We are also seeing it timeout fairly regularly during the install process. To keep the conde consistent I create a PR which will stop it timing out. It still slow but it seems most of the delay I am seeing is with the apt-get instal azure-cli
step taking a long time to run, so not much I can do to speed that up
PR is here: https://github.com/CircleCI-Public/azure-cli-orb/pull/21
cause of issue - https://github.com/Azure/azure-cli/issues/18531
$ sudo apt-get install azure-cli
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
azure-cli
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
Need to get 79.4 MB of archives.
After this operation, 1,049 MB of additional disk space will be used.
Get:1 https://packages.microsoft.com/repos/azure-cli jammy/main amd64 azure-cli all 2.38.0-1~jammy [79.4 MB]
26% [1 azure-cli 25.5 MB/79.4 MB 32%] 101 kB/s 10min 54s
@karlparry @HSerg Can you verify is this fix from Microsoft helps with the download speed?
https://github.com/microsoft/linux-package-repositories/issues/13#issuecomment-1192670366
@jckeme-rs Yes, the issue is resolved.
Speed has increased, but as the Microsoft gets network slowness from time to time anyway, it may not be a bad idea to increase this timeout in case it happens again. Can't remember if you can in CircleCI orbs, parameterising the timeout so down stream users can override it when needed.
Orb version
1.2.0 - 1.22
What happened
Expected behavior
Installation ideally took < 40 seconds, but now it takes an average of about 4 minutes per job.
If possible, the install process should be optimized to only perform apt update once, as opposed to twice during the install process, if the verification will always have issues due to package verification failures. If installation at this pace becomes a norm, then frequent output to STDOUT should be made to keep the pipeline active pending the installation process.