Hi Elijah,
thanks a lot once again for your help, I'm processing the patch right now :)
Have a nice day, all the best!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Oct 3, 2011 at 3:32 AM, Elijah Zupancic eli...@zupancic.name wrote:
I've finally got a little
I've finally got a little time to work on Chain again. Anyways, I have
logged this bug in Jira (https://issues.apache.org/jira/browse/CHAIN-60) and
uploaded a patch to fix it. In the future, I think it would it would be
helpful in unit test were randomized on each execution in order to prevent
tested both with java5 and java6 using mvn3... should we expect
different results when using mvn2 to run tests?
Many thanks in advance, have a noce day!!!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, Sep 21, 2011 at 10:21 PM, Continuum@vmbuild
On 22 September 2011 09:52, Simone Tripodi simonetrip...@apache.org wrote:
tested both with java5 and java6 using mvn3... should we expect
different results when using mvn2 to run tests?
No. That indicates a bug in source or test code.
Can you try locally using Maven 2?
It's possible to
Hi guys,
I tested on the below environment and it works like a charm. I suspect
it is something related to continuum environment.
--
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version:
On 22 September 2011 10:24, Maurizio Cucchiara mcucchi...@apache.org wrote:
Hi guys,
I tested on the below environment and it works like a charm. I suspect
it is something related to continuum environment.
Or a timing issue?
I don't think the issue can just be dismissed - after all, a user
Or a timing issue?
are you talking about execution order? it was the first thing that
came into my mind, but as far as I can see (I probably know chain less
than you) it is not an order-related issue (the test tries to open
simply an xml file and load some element into a collection, then it
I don't think the issue can just be dismissed - after all, a user
might have the same environment as Continuum ...
I totally agree with you.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands,
On 22 September 2011 10:40, Maurizio Cucchiara mcucchi...@apache.org wrote:
Or a timing issue?
are you talking about execution order? it was the first thing that
came into my mind, but as far as I can see (I probably know chain less
than you) it is not an order-related issue (the test tries to
Ha! This was the exact error that I reported back in early August. I was
tearing my hair out trying to figure out why it only happened on my laptop
and not on any other machine. I'm so glad you found this. What exactly did
you configure differently to make this happen? On my laptop, if I ran the
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=12321projectId=69
Build statistics:
State: Failed
Previous State: Failed
Started at: Mon 19 Sep 2011 16:24:18 +
Finished at: Mon 19 Sep 2011 16:24:35 +
Total time: 16s
Build Trigger: Schedule
uh...
I just ran tests on my laptop with both jdk1.5 and 1.6 and they run fine...
do you have any idea?
many thanks in advance!
Simo
$ mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: /Applications/apache-maven-3.0.3
Java version: 1.5.0_30, vendor: Apple Inc.
Java
The first thing that comes into my mind is: Did you try to run on
maven 2 (the version of continuum is 2.2.1) ?
Maurizio Cucchiara
On 19 September 2011 18:29, Simone Tripodi simonetrip...@apache.org wrote:
Apache Maven 2.2.1
HA! no I didn't, my fault, I need do (re)download it and then try :)
thanks for the hint!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Sep 19, 2011 at 6:35 PM, Maurizio Cucchiara
mcucchi...@apache.org wrote:
The first thing that comes into my mind is: Did you
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=12198projectId=69
Build statistics:
State: Failed
Previous State: Failed
Started at: Fri 16 Sep 2011 22:24:40 +
Finished at: Fri 16 Sep 2011 22:25:04 +
Total time: 24s
Build Trigger: Schedule
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=12103projectId=69
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 14 Sep 2011 22:23:55 +
Finished at: Wed 14 Sep 2011 22:24:16 +
Total time: 21s
Build Trigger: Schedule
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=12058projectId=69
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 13 Sep 2011 21:24:38 +
Finished at: Tue 13 Sep 2011 21:25:04 +
Total time: 25s
Build Trigger: Schedule
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=12061projectId=69
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 13 Sep 2011 22:23:54 +
Finished at: Tue 13 Sep 2011 22:24:14 +
Total time: 20s
Build Trigger: Forced
Build
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=12062projectId=69
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 13 Sep 2011 22:25:54 +
Finished at: Tue 13 Sep 2011 22:26:05 +
Total time: 11s
Build Trigger: Forced
Build
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=12009projectId=69
Build statistics:
State: Failed
Previous State: Failed
Started at: Mon 12 Sep 2011 18:48:14 +
Finished at: Mon 12 Sep 2011 18:48:35 +
Total time: 21s
Build Trigger: Schedule
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=11991projectId=69
Build statistics:
State: Failed
Previous State: Ok
Started at: Sun 11 Sep 2011 19:09:12 +
Finished at: Sun 11 Sep 2011 19:09:37 +
Total time: 25s
Build Trigger: Schedule
Build
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=10748projectId=69
Build statistics:
State: Failed
Previous State: Ok
Started at: Tue 2 Aug 2011 15:48:12 +
Finished at: Tue 2 Aug 2011 15:48:24 +
Total time: 11s
Build Trigger: Forced
Build
22 matches
Mail list logo
