From: Greg.mpls@... Date: 2019-05-31T21:42:49+00:00 Subject: [ruby-core:92919] [Ruby trunk Misc#15892] Appveyor - full MSYS2 update - 5:25 Issue #15892 has been updated by MSP-Greg (Greg L). 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: https://ci.appveyor.com/project/MSP-Greg/testing-appveyor/builds/24958423 Fice 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... ---------------------------------------- Misc #15892: Appveyor - full MSYS2 update - 5:25 https://bugs.ruby-lang.org/issues/15892#change-78295 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: ---------------------------------------- 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 -- https://bugs.ruby-lang.org/ Unsubscribe: