On Feb 4, 2014, at 12:50 PM, Dan Berindei <dan.berindei(a)gmail.com> wrote:
On Tue, Feb 4, 2014 at 2:36 PM, Galder Zamarreño <galder(a)redhat.com> wrote:
Narrowing down the list now, since this is a problem of how our CI is doing builds.
These logs are retrieved from [1].
Dunno how our CI is configured but this is odd. Seems like the build is halt due to test
failures, but it continues somehow? I mean, the jars are not being produced properly, but
the build is not halting.
We run the build with -fn (fail-never), so the build should never be halted because of a
test failure. The configuration is
here:http://ci.infinispan.org/admin/editRunType.html?id=buildType:bt8&...
It’s about time we did the following:
1) Any test failures should halt the build there and then. IOW, do not continue the build
at all.
Will having 100 tests in one run and 2000 tests in another really help?
2) Any tests that fail randomly should be disabled.
Doing this in past didn't seem to help: tests were disabled and never re-enabled
again. IMO we should fight to get the suite green and then any intermittent failure should
be considered a blocker and treated as the highest prio.
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org)