Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97217
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error)
To: "'Stanislav Malyshev'" <smalyshev@gmail.com>,
	"'PHP Internals'" <internals@lists.php.net>
References: <94e879ab-ec3b-c758-7ed6-340c9c20543f@gmail.com>
In-Reply-To: <94e879ab-ec3b-c758-7ed6-340c9c20543f@gmail.com>
Date: Mon, 28 Nov 2016 12:47:13 +0100
Message-ID: <00d101d2496d$2b2d55e0$818801a0$@belski.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQHzRKzYWEIJdUHzsdzM4+t/pH06aaCsS5Ag
Content-Language: en-us
Subject: RE: [PHP-DEV] unstable Travis CI builds
From: anatol.php@belski.net ("Anatol Belski")

Hi Stas,

> -----Original Message-----
> From: Stanislav Malyshev [mailto:smalyshev@gmail.com]
> Sent: Monday, November 28, 2016 12:54 AM
> To: PHP Internals <internals@lists.php.net>
> Subject: [PHP-DEV] unstable Travis CI builds
>=20
> Hi!
>=20
> I've noticed that recently there is a real lot of random failures on =
Travis CI. E.g.
> this build:
> https://travis-ci.org/php/php-src/builds/179298649
>=20
> two tests fail: ext/sysvsem/tests/nowait.phpt and
> sapi/cli/tests/php_cli_server_017.phpt
> Im different builds different random tests fail. Did we change =
something in
> Travis config or settings that may be causing this? It is really not =
good that our
> builds always fail in random places, we need to improve the stability =
or look for
> some other solution...
> --
These fails started about two weeks ago. I was investigating on them, =
especially before tagging the scheduled RC. I couldn't find any =
suspicious change, that could lead to the fails. My usual test =
environment didn't reproduce those, and I became a confirmation about =
the not reproducibility of those from a couple of other sources. So =
where I stand currently - it seems possible, that something on the =
Travis environment has changed, so then the VM runs slower. That would =
explain impacts on the  I/O and timing tests, fe for CLI server tests =
fail sporadically, same for cURL and others. If we've contact to the =
Travis support, maybe it'd make sense to ask for possible changes on the =
side of Travis or ask to check the healthiness of the underlying HW.

Regards

Anatol