On Sun, 9 Oct 2016 20:07:21 -0400, Rob Tompkins wrote:
I'm indifferent on the documentation here. But, I figure the changes
should be in there either way.
Sure.
If we think it better to have two jiras
to sufficiently document the change, I'll back it out, make just the
.travis.yml change and open a separate jira for the RetryRunner.
No need to worry more about it.
The nit-picking about my little remark is enough of a trace.
Regards,
Gilles
Just let me know what you guys think is best, and I'll head that
direction.
Cheers,
-Rob
On Oct 9, 2016, at 7:51 PM, Emmanuel Bourg <[email protected]>
wrote:
Le 10/10/2016 à 01:40, Gilles a écrit :
For months, Travis consistently did not work (i.e. even when
that non-deterministic passed, which it does 99% of the time
for truly uniform RNG) even though local and Jenkins builds
went fine.
The problem reported as MATH-1387 was about what was wrong with
the Travis configuration. [Thanks to Rob for fixing it.]
The bug isn't titled "The Travis configuration is broken", it's
titled
"Travis does not work", this means the resolution may include
configuration fixes *and* test stabilization. Rob even pasted the
log of
the test failure in the bug so the intent of this commit is clear.
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
