You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/29 21:58:00 UTC
[jira] [Work logged] (TOMEE-3931) fix example/cucumber-jvm
[ https://issues.apache.org/jira/browse/TOMEE-3931?focusedWorklogId=764518&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-764518 ]
ASF GitHub Bot logged work on TOMEE-3931:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Apr/22 21:57
Start Date: 29/Apr/22 21:57
Worklog Time Spent: 10m
Work Description: cesarhernandezgt commented on PR #875:
URL: https://github.com/apache/tomee/pull/875#issuecomment-1113786036
> I am wondering about the re-generated BOM files. Adding a new shade dep shouldn't alter them? Perhaps an older (?) local state? Or did we alter the TomEE Jakarta API snapshot recently?
I wondered the same, I pull the latest master and after building without a test but with -Pno-examples, boms are updated. I opened a separate PR to double check that this was not related to adding a shade dep: https://github.com/apache/tomee/pull/876
If 876 is fine, we can merge and I'll rebase pr 875, or we can just go ahead with 875 and I would drop 876
Issue Time Tracking
-------------------
Worklog Id: (was: 764518)
Remaining Estimate: 0h
Time Spent: 10m
> fix example/cucumber-jvm
> -------------------------
>
> Key: TOMEE-3931
> URL: https://issues.apache.org/jira/browse/TOMEE-3931
> Project: TomEE
> Issue Type: Sub-task
> Affects Versions: 9.0.0-M7
> Reporter: Cesar Hernandez
> Assignee: Cesar Hernandez
> Priority: Major
> Fix For: 9.0.0-M8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Current Master CI shows this test if failing. I was able to reproduce the issue locally too:
> {code:java}
> T E S T S
> -------------------------------------------------------
> Running org.superbiz.cucumber.CucumberTest
> 0 Scenarios
> 0 Steps
> 0m0.149s
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.411 sec <<< FAILURE!
> Feature: Hello Time elapsed: 0.406 sec <<< ERROR!
> java.lang.NoClassDefFoundError: javax/ejb/embeddable/EJBContainer
> at cucumber.runtime.java.openejb.OpenEJBObjectFactory.start(OpenEJBObjectFactory.java:32)
> at cucumber.runtime.java.JavaBackend.buildWorld(JavaBackend.java:115)
> at cucumber.runner.Runner.buildBackendWorlds(Runner.java:120)
> at cucumber.runner.Runner.runPickle(Runner.java:38)
> at cucumber.runtime.junit.PickleRunners$NoStepDescriptions.run(PickleRunners.java:146)
> at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
> at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
> at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
> at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.ClassNotFoundException: javax.ejb.embeddable.EJBContainer
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 37 more
> Results :
> Tests in error:
> Feature: Hello: javax/ejb/embeddable/EJBContainer
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [ERROR] There are test failures.
> Please refer to /home/jenkins/jenkins-agent/workspace/Tomee/master-build-full/examples/cucumber-jvm/target/surefire-reports for the individual test results.
> [JENKINS] Recording test results {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)