it also fails on our hudson job
https://hudson.qa.jboss.com/hudson/job/hibernate-search-master/org.hibernate$hibernate-search-orm/6/testReport/org.hibernate.search.test.engine.optimizations/CollectionUpdateEventTest/testWithClassBridge/
---
Strong Liu
http://hibernate.org
http://github.
I haven't seen this one failing yet. The JGroups tests, but not the
CollectionUpdateEventTest. Scary.
--Hardy
On Wed, 28 Sep 2011 10:46:03 +0200, Sanne Grinovero
wrote:
> To resume this thread, the bad news is that it started to fail for me
> too: often, but not consistently.
> It only fails
To resume this thread, the bad news is that it started to fail for me
too: often, but not consistently.
It only fails when running the full testsuite from commandline, it
succeeds when running it as a single test from commandline
mvn clean test
-Dtest=org.hibernate.search.test.engine.optimization
This is the configuration of the surefire plugin when I run maven in debug mode:
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-surefire-plugin:2.7.2:test from plugin
realm ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:2.7.2,
parent: sun.misc.Launcher$AppClassLoader@123
Hi,
first of all your execution order is completely different.
Looking a little bit deeper into it I noticed that my execution order is
alphabetical
which is expected since surefire 2.7
(http://jira.codehaus.org/browse/SUREFIRE-321).
Assuming alphabetical ordering is not broken on your machin
The following are the information of the machine I'm using right now
CentOS release 5.5 (Final)
Apache Maven 3.0.3 (r1075438; 2011-02-28 17:31:09+)
Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.18-194.32.1.
Hi,
for all it's worth, the build is working fine for me as well.
What OS, JVM and maven version are you using?
I am asking, because this might influence the order in which the tests are
executed.
There might be some interdependencies between tests (and some failing
cleanup) which
only occurs
It seems it fails only if I execute it among all the other tests.
It works if I run
mvn test
-Dtest=org.hibernate.search.test.engine.optimizations.CollectionUpdateEventTest
On Fri, Aug 19, 2011 at 10:14 AM, Sanne Grinovero wrote:
> I'm puzzled, but will need more clues.
>
> # short answer
> N
I'm puzzled, but will need more clues.
# short answer
No, no special options are required.
# more details
Only two categories of tests require special care:
Byteman
Some tests need the Byteman agent running, but this is taken care of
by Maven (but is not configuring the IDE automagically)
JGrou
I've cloned it from scratch and the test fails
systematically...actually it failed today on an other PC too.
Maybe some parameter that needs to be set?
On Thu, Aug 18, 2011 at 10:35 PM, Sanne Grinovero wrote:
> Hi Davide,
> I can't reproduce the problem, even re-running that same test several
>
Hi Davide,
I can't reproduce the problem, even re-running that same test several
times. Are you sure you have a clean clone from master?
("git reset --hard" will remove all changes you might have around)
Cheers,
Sanne
2011/8/18 Davide D'Alto :
> Hi,
> I've just pull the changes from the hibernate
11 matches
Mail list logo
