Hi all, At one point when I worked on BVal I remember we were fully green for the entire suite. I realized last week that a test was continuously failing. I tried running it locally and it did fail on IntelliJ, alone but was failing as part of the suite.
Using the command line, it failed in all cases. I started debugging without really finding what was the issue until I stepped down into Arquillian. After looking a bit more deeply I found that it worked with Arquillian until 1.7.0.Alpha9 where it started failing. They did a small change to support parallel execution with TestNG and it had a bad impact on this particular test org.hibernate.beanvalidation.tck.tests.bootstrap.customprovider.BootstrapNonAvailableValidationProviderTest.arquillianAfterSuite <https://ci-builds.apache.org/job/Tomee/job/master-build-full/org.apache.tomee$bval-tomee/778/testReport/org.hibernate.beanvalidation.tck.tests.bootstrap.customprovider/BootstrapNonAvailableValidationProviderTest/arquillianAfterSuite/> The test actually runs perfectly. The clean up after the test successfully returns is failing. Anyways, long story short, I did remove the parallel stuff so we could remain in the last version of TestNG and Arquillian but now I get the following error locally org.hibernate.beanvalidation.tck.tests.constraints.groups.groupconversion.containerelement.InvalidGroupDefinitionsOnContainerElementsTest I'll be looking at TestNG because this seems to be the thing breaking this test... The issue is that the API changed between 6 and 7 and there is an execution failure due a signature change. So to use the recent Arquillian version we need a recent TestNG which fails a specific test. If we get a down grad, then we get another test to fail. This seems endless. I'm wondering if there is something we can do in our adapter to help. It is taking much more time than what I was expecting. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com
