tag:help.appveyor.com,2012-11-13:/discussions/problems/27777-msys-build-on-vs-2019-image-is-considerably-slower-than-vs-2017-oneAppVeyor: Discussion 2021-02-26T21:54:33Ztag:help.appveyor.com,2012-11-13:Comment/484842162021-02-26T20:07:01Z2021-02-26T20:07:01ZMSYS build on VS 2019 image is considerably slower than VS 2017 one <div><p>We seem to be hitting the same issue with MSYS2 builds:<br>
I recently switched to the VS2019 image [1] because of the outdated MSYS2 version (that was becoming hard to update and maintain) in the default image. Since then builds do not even come close to finishing despite the 1:30h limit of our project.</p>
<p>Previously 1:30h was plenty of time to finish builds.</p>
<p>[1] <a href="https://ci.appveyor.com/project/inkscape/inkscape/builds/37807964">https://ci.appveyor.com/project/inkscape/inkscape/builds/37807964</a></p></div>eduard.braun2tag:help.appveyor.com,2012-11-13:Comment/484842162021-02-26T20:10:02Z2021-02-26T20:10:02ZMSYS build on VS 2019 image is considerably slower than VS 2017 one <div><p>Does not seem to be an uncommon issue: <a href="https://help.appveyor.com/discussions/problems/25195-msys-build-on-vs-2019-image-is-twice-as-slow-as-on-vs-2017-one">https://help.appveyor.com/discussions/problems/25195-msys-build-on-...</a></p></div>eduard.braun2tag:help.appveyor.com,2012-11-13:Comment/484842162021-02-26T21:14:50Z2021-02-26T21:14:50ZMSYS build on VS 2019 image is considerably slower than VS 2017 one <div><p>I remember experimenting with different cloud providers and <code>Visual Studio 2019</code> builds were slower on Azure, GCE and bare-metal Hyper-V. I suspect it's somehow related to Windows Server 2019 as a base image. Images on all providers are not related with each other and made separately.</p>
<p>I'd like to do another experiment with your project. Is <code>master</code> branch green now? Does it run OK on both VS 2017 and VS 2019 images?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/484842162021-02-26T21:54:30Z2021-02-26T21:54:30ZMSYS build on VS 2019 image is considerably slower than VS 2017 one <div><p>In theory it should run on VS2017 and VS2019 alike and should produce identical results (it updates MSYS2 automatically).</p>
<p>However the MSYS2 in the VS2017 image was too old previously, so that it could not be updated easily anymore (outdated keyring; outdated pacman without zstd support) which is why I switched to the VS2019 image in the first place (it was recommended in a few places were people were complaining about the outdated MSYS2).</p></div>eduard.braun2