polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Merlin <p...@nosphere.org>
Subject Re: Flaky tests and CI
Date Wed, 15 Jun 2016 17:24:21 GMT
Niclas Hedhman a écrit :
> I agree.

Metrics tests will now be retried 3 times up until success.

> I am even at the point of killing Scheduler completely for now, since there
> are critical bugs in it, and scheduling might be better done with external
> trigger.

Yeah, let's ditch it!

> Rest tests, sure go ahead. I also think that it need a major overhaul,
> since none of us are familiar with the library and can't support it.

Hum, I won't dive into this and do any overhaul :)
But, I added a configuration to the "admin" server so we can set the port.
And the tests now use a dynamically allowed free port.
This should prevent the CI builds to fail intermitently and send useless
emails to dev@.


> On Jun 15, 2016 01:31, "Paul Merlin" <paul@nosphere.org> wrote
>> Gang,
>> We have some flaky tests.
>> We know about Metrics and Scheduler tests.
>> Both are time-related.
>> For Metrics, maybe a simple retry strategy would do. WDYT Niclas?
>> The Scheduler library situation is not good.
>> I'm tempted to simply disable the tests until a rewrite occurs.
>> And the new kid on the block is the Rest library.
>> Tests started to fail from time to time with root cause of "Address
>> already in use".
>> The tests starts the rest server on port 8192 that may be used by
>> something else, on o.a.builds it is sometime used by something, it
>> appears to be more frequent recently.
>> The tests should be adapted to use FreePortFinder from testsupport.
>> Cheers

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message