Misc #15892


Appveyor - full MSYS2 update - 5:25

Added by MSP-Greg (Greg L) about 3 years ago. Updated about 3 years ago.



Just tried a full MSYS2 update on Appveyor, and it took 5:25.

The most recent Ruby build (which finished within minutes of the MSYS2 update) took about 39 minutes, but it may have been waiting. Past builds occasionally take 45 to 50 minutes, but they may have also been waiting. Most ruby-loco builds are in the low 30's, but some builds take 45 minutes.

Hence, the 5:25 time could be longer, and there is also the potential for network failures, since quite a few files may be downloaded.

Just wanted to clarify the trade off between longer builds times vs occasional failures & some extra commits..

Feel free to close.

JFYI... Have a good weekend, Greg

Updated by k0kubun (Takashi Kokubun) about 3 years ago

Thanks to share. As the last appveyor.yml update has worked for only 3 days, the "full MSYS2 update" would be worth trying.

However, as I'm not familiar with MSYS2 and pacman that much, I don't know what exact code you imagine by "full MSYS2 update" yet. I may take a look when I find a CI failure by myself next time (I was sleeping this time).

Updated by MSP-Greg (Greg L) about 3 years ago

I used:

pacman -Syuu --noconfirm --noprogressbar --nodeps
pacman -Suu  --noconfirm --noprogressbar --nodeps

With the current state of the Appveyor MSYS2 system, both are needed. The -y option updates the package database.

The Appveyor log is here:

Five minutes added to 30+ is not great, but not terrible. I've got some repos I support where the Appveyor CI takes less than ten minutes. Adding five to that...

Updated by k0kubun (Takashi Kokubun) about 3 years ago

  • Status changed from Open to Closed

Thanks. I managed to pass the CI with the idea in, but it added 8 minutes, not 5.

I'm slightly reluctant to add 8 minutes to msys2 build time, so I'll consider applying it when AppVeyor fails on package installation next time.


Also available in: Atom PDF