On Feb 4, 2014, at 12:50 PM, Dan Berindei dan.berin...@gmail.com wrote:
On Tue, Feb 4, 2014 at 2:36 PM, Galder Zamarreño gal...@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
On 04 Feb 2014, at 09:37, Stuart Douglas stuart.w.doug...@gmail.com wrote:
This looks like an issue with your environment. The modules directory is
static. Wildfly does not contain any code that messes with it. I would say
the culprit is probably something in either your build process or
On 04 Feb 2014, at 10:01, Stuart Douglas stuart.w.doug...@gmail.com wrote:
On Tue, Feb 4, 2014 at 11:00 AM, Stuart Douglas stuart.w.doug...@gmail.com
wrote:
Yes, there is nothing in the server code that modified the modules directory.
Well, except for the new patching stuff, but
On 04 Feb 2014, at 10:38, Stuart Douglas stuart.w.doug...@gmail.com wrote:
It is almost certainly something to do with this:
module-def name=org.infinispan.server.rest
src=${infinispan.server.modules.dir}
maven-resource-with-classifier group=org.infinispan
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,
On Tue, Feb 4, 2014 at 2:36 PM, Galder Zamarreño gal...@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
On 04 Feb 2014, at 13:36, Galder Zamarreño gal...@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,
On 04 Feb 2014, at 13:50, Dan Berindei dan.berin...@gmail.com wrote:
On Tue, Feb 4, 2014 at 2:36 PM, Galder Zamarreño gal...@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
On Tue, Feb 4, 2014 at 3:03 PM, Galder Zamarreño gal...@redhat.com wrote:
On 04 Feb 2014, at 13:50, Dan Berindei dan.berin...@gmail.com wrote:
On Tue, Feb 4, 2014 at 2:36 PM, Galder Zamarreño gal...@redhat.com
wrote:
Narrowing down the list now, since this is a problem of how our CI is
On 04 Feb 2014, at 14:47, Dan Berindei dan.berin...@gmail.com wrote:
On Tue, Feb 4, 2014 at 3:03 PM, Galder Zamarreño gal...@redhat.com wrote:
On 04 Feb 2014, at 13:50, Dan Berindei dan.berin...@gmail.com wrote:
On Tue, Feb 4, 2014 at 2:36 PM, Galder Zamarreño gal...@redhat.com
All,
Sanne, Pedro, Dan and I had a very productive discussion on IRC on this topic
[1].
We’ve decided that instead of disabling tests, we need them to run in order to
get recent stacktraces, logs, etc. So, we’ve decided to create a new test group
called “unstable”. This test group would only
For the record, -Dmaven.test.failure.ignore seems to do the right thing,
and the JDK7 build now only has 7 test failures (+ 4 ignored):
http://ci.infinispan.org/viewLog.html?buildId=5912tab=buildResultsDivbuildTypeId=bt8
On Tue, Feb 4, 2014 at 4:36 PM, Galder Zamarreño gal...@redhat.com wrote:
12 matches
Mail list logo
