This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
Content-Type: text/plain; charset=UTF-8
On Tue 01 Jul 2014 06:33:08 PM CEST, Nir Soffer wrote:
We can see that the test succeeded:
Ran 551 tests in 264.511s
But hudson failed:
FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Cha=
nnel$OrderlyShutdown: java.util.concurrent.TimeoutException: Ping started=
on 1404230202100 hasn't completed at 1404230442456
This is a recurring problem in the CI. We need to eliminate these error=
waste developers time, and worse, cause them to ignore failures.
Please give this issue higher priority.
Infra mailing list
Not long ago we started a thread to try and determine if a job failed=20
due to test error (meaning, one of the tests failed) or infra error=20
(anything else, for example, network error, timeout...).
iirc the last proposal was to generate a test file with a strict format=20
that the job will check, and if not found or malformed it will be=20
assumed infra issue, and if well formed, the file itself would=20
determine if it passed of there were any test errors.
But no specific format was proposed, or file for that matter. I would=20
be glad with just two messages (very strict format) in the log, tests=20
ran and passed, and tests ran and did not pass. We are already doing=20
that on a few jobs with good results for other projects.
So if you want this to get pushed, please, feel free to provide a=20
deterministic way for ci to detect if the tests did run properly and=20
the result of the run. This also wastes infra time so please provide a=20
Also, can you open a ticket on https://fedorahosted.org/ovirt/newticket=20
for any specific request? If it's not there, it has no priority. We are=20
trying to open there all the issues so we can manage them better and=20
leave the list for discussions and announcements.
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
RHT Global #: 82-62605
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----