Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104020
MIME-Version: 1.0
Date: Sat, 2 Feb 2019 13:18:55 +0100
Message-ID: <CAF+90c9wcAFmFje0jHKbpUer-Vu1v_8STeZbUPxVSeupAfWuNw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007563810580e84422"
Subject: AppVeyor timeouts -- Migrate to Azure Pipelines?
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000007563810580e84422
Content-Type: text/plain; charset="UTF-8"

Hi internals,

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.

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.

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?

Regards,
Nikita

--0000000000007563810580e84422--