On 04 Feb 2014, at 09:37, Stuart Douglas 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 your test
> suite.
Corre
On 04 Feb 2014, at 10:01, Stuart Douglas wrote:
>
>
>
> On Tue, Feb 4, 2014 at 11:00 AM, Stuart Douglas
> wrote:
> Yes, there is nothing in the server code that modified the modules directory.
>
> Well, except for the new patching stuff, but that is not really relevant here.
The testsuite
On 04 Feb 2014, at 10:38, Stuart Douglas wrote:
> It is almost certainly something to do with this:
>
> src="${infinispan.server.modules.dir}">
>
> artifact="infinispan-server-rest" classifier="classes" />
>
>
>
> I guess sometimes the classes artefact is being attached as a refe
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 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 co
On 04 Feb 2014, at 13:36, Galder Zamarreño 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 con
On 04 Feb 2014, at 13:50, Dan Berindei wrote:
>
> On Tue, Feb 4, 2014 at 2:36 PM, Galder Zamarreño 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
On Tue, Feb 4, 2014 at 3:03 PM, Galder Zamarreño wrote:
>
> On 04 Feb 2014, at 13:50, Dan Berindei wrote:
>
> >
> > On Tue, Feb 4, 2014 at 2:36 PM, Galder Zamarreño
> wrote:
> > Narrowing down the list now, since this is a problem of how our CI is
> doing builds.
> >
> > These logs are retrieve
On 04 Feb 2014, at 14:47, Dan Berindei wrote:
>
>
>
> On Tue, Feb 4, 2014 at 3:03 PM, Galder Zamarreño wrote:
>
> On 04 Feb 2014, at 13:50, Dan Berindei wrote:
>
> >
> > On Tue, Feb 4, 2014 at 2:36 PM, Galder Zamarreño wrote:
> > Narrowing down the list now, since this is a problem of ho
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 b
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=5912&tab=buildResultsDiv&buildTypeId=bt8
On Tue, Feb 4, 2014 at 4:36 PM, Galder Zamarreño wrote:
> All,
>
> Sann
On Feb 4, 2014, at 12:50 PM, Dan Berindei wrote:
>
> On Tue, Feb 4, 2014 at 2:36 PM, Galder Zamarreño 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. See
On Feb 4, 2014, at 12:52 PM, Galder Zamarreño wrote:
>
> On 04 Feb 2014, at 13:36, Galder Zamarreño 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 o
13 matches
Mail list logo
