It seems that the CDI Extensions are not running. I first thought that it was because of this setting: openejb.cdi.activated-on-ejb, but it seems to have the same effect.
I’ll keep looking. > On 19 Dec 2018, at 13:21, Jonathan Gallimore <[email protected]> > wrote: > > I see the issue with surefire:test@test-tomee-remote-plus too. Trying to > get some more information. > > Jon > > On Wed, Dec 19, 2018 at 12:39 PM Jonathan Gallimore < > [email protected]> wrote: > >> Here's my full output: >> https://gist.github.com/jgallimore/ead9d0a218d862596858d7dc72bd6f62 >> >> There's a few failures for test-tomee-remote-plus, and it gets worse when >> testing test-tomee-webapp-* executions. >> >> Hope that helps. Neat trick with the command line @test-tomee-remote-plume >> - thanks for that. >> >> Jon >> >> >> >> On Wed, Dec 19, 2018 at 12:15 PM Roberto Cortez >> <[email protected]> wrote: >> >>> I’m using this sample command now: >>> mvn -Pall-adapters clean test-compile >>> surefire:test@test-tomee-remote-plume >>> -Dtest=org.apache.openejb.arquillian.tests.filter.AllFilterTest >>> >>> It seems to run fine on plus but not on plume. Investigating... >>> >>>> On 19 Dec 2018, at 11:44, Roberto Cortez <[email protected]> >>> wrote: >>>> >>>> Maybe it does run first. The problem is that the build is killed, so >>> you don’t have a test report output. You have to go and manually search the >>> logs. >>>> >>>> What is the exact test you see failing? I see a failure in the JMS >>> project with a simple clean install: >>>> JMSInjectionTest.testJMSInjection:68->validateTest:74 » IO Server >>> returned HTT >>>> >>>>> On 19 Dec 2018, at 11:18, Jonathan Gallimore < >>> [email protected]> wrote: >>>>> >>>>> I'm not sure of the module ordering, but I thought this ran first. I'll >>>>> check the CI output. >>>>> >>>>> If you run a build without tests, and then run `mvn -Pall-adapters >>> clean >>>>> install` >>>>> in arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests, >>>>> you'll see the issue. >>>>> >>>>> Jon >>>>> >>>>> On Wed, Dec 19, 2018 at 11:00 AM Roberto Cortez >>> <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Jon, >>>>>> >>>>>> I can have a look. >>>>>> >>>>>> It’s been hard to figure issues out, since we were not able to >>> stabilize >>>>>> the TomEE build in build bot. >>>>>> >>>>>> Apparently, it just keeps getting stuck in CDI TCK and timeouts. >>>>>> >>>>>> Cheers, >>>>>> Roberto >>>>>> >>>>>>> On 19 Dec 2018, at 10:28, Jonathan Gallimore < >>>>>> [email protected]> wrote: >>>>>>> >>>>>>> I'm not sure if this is being discussed on other threads, but it >>> looks >>>>>> like >>>>>>> we have an issue with our arquillian tests failing. >>>>>>> >>>>>>> I did a git bisect late last night, and it looks like it was >>> introduced >>>>>>> with the addition of microprofile to the plume and plus >>> distributions. >>>>>> I'm >>>>>>> still going through my build output, but it looks like we have a >>> couple >>>>>> of >>>>>>> issues. >>>>>>> >>>>>>> Firstly, it looks like something in microprofile adds JAX-RS to the >>> app, >>>>>>> and that seems to get priority over everything, so, for example, if I >>>>>>> deploy a servlet with a URL mapping of "/" I can't get to it - I'll >>>>>> always >>>>>>> get a 404. >>>>>>> >>>>>>> There seems to be another issue that prevents apps from deploying >>> too. >>>>>>> >>>>>>> I'll continue analysis and post further details, but also don't want >>> to >>>>>>> tread on toes, so if you're already looking at this, please shout! >>>>>>> >>>>>>> Cheers >>>>>>> >>>>>>> Jon >>>>>> >>>>>> >>>> >>> >>>
