On 02.02.2019 at 13:18, Nikita Popov wrote: > Since some time ago (not sure how long) our AppVeyor builds have been > timing out more often than not, to the point that I've started ignoring > failing AppVeyor builds entirely.
Indeed, this is particularly annoying for RMs. > I just learned about the Azure Pipelines ( > https://azure.microsoft.com/en-us/services/devops/pipelines/) offering, > which offers open source projects 10 parallel builds with unlimited > minutes. Assuming there's no other catch here, it might be worthwhile to > migrate our Windows CI jobs to Azure Pipelines. An alternative to consider is using Travis for Windows CI[1], too. > Independently of that, it would be great if someone on a Windows > environment could look into the issue of AppVeyor timeouts. While PHP is > known to be slower on Windows, I find it somewhat odd that our AppVeyor > builds routinely take more than 60 minutes, while Travis builds usually > finish in 20 minutes. Based on build logs, running tests on AppVeyor often > takes ~45 minutes, while it takes ~15 minutes on Travis. Might there be a > legitimate performance issue here, that was caused by a recent-ish (last > month or so) change? To my knowledge, Appveyor “always” was way slower than Travis, and maybe we're hitting the timeouts only now, since the size of the test suite has increased. Since our Appveyor CI runs with slow tests enabled, it might be worth a try to disable these. I've just submitted PR #3789[2] to see whether that would make a big difference. [1] <https://blog.travis-ci.com/2018-10-11-windows-early-release> [2] <https://github.com/php/php-src/pull/3789> -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
