Tried on linux, works. Well, the test failed, but at least maven wasn't terminated abruptly.
On Windows, still getting the same message, but this time a new problem: C:\Users\Ferdi_S672\Documents\Personal\Projects\tomee (master -> origin) λ "C:\Program Files\Java\jdk1.8.0_161\jre\bin\java" -javaagent:C:\Users\Ferdi_S672\Documents\Personal\Projects\tomee\container\openejb-core/target/openejb-javaagent-8.0.0-SNAPSHOT.jar -Dopenejb.classloader.forced-skip=org.apache.openejb.jee.,org.apache.openejb.api. -Dopenejb.classloader.forced-load=org.apache.openejb -enableassertions -Dopenejb.descriptors.output.folder=./dump/ -Dorg.apache.activemq.SERIALIZABLE_PACKAGES=org,java -jar C:\Users\FERDI_~1\AppData\Local\Temp\surefire7924936420170998629\surefirebooter7022447534707396131.jar C:\Users\Ferdi_S672\AppData\Local\Temp\surefire7924936420170998629 2018-11-28T09-38-01_693-jvmRun1 surefire50447437123862647tmp surefire_728217078389408279960tmp Error: Unable to access jarfile C:\Users\FERDI_~1\AppData\Local\Temp\surefire7924936420170998629\surefirebooter7022447534707396131.jar The referenced jar in Temp wasn't there, so the test failed. On 11/27/2018 10:37 PM, Jonathan Gallimore wrote: > I managed to reproduce the issue - looks like it works ok under Cygwin on > my machine, but not in a DOS box. A brief test has shown some better > results with surefire 2.18.1 - can you give that a try? > > Jon > > On Tue, Nov 27, 2018 at 10:40 AM Jonathan Gallimore < > jonathan.gallim...@gmail.com> wrote: > >> The build on my Windows machine here ran for ages, and then the machine >> rebooted for some weird reason. It seemed to get further through the >> openejb-core tests than yours from the log I have here. Going to run it >> again. Thanks for including the command, that is really useful. >> >> For completeness, here's my java -version and mvn -v output: >> >> jon@DESKTOP-D9NMDPA /cygdrive/c/Users/jon/dev/tomee >> $ java -version >> openjdk version "1.8.0_181" >> OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_181-b13) >> OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.181-b13, mixed mode) >> >> jon@DESKTOP-D9NMDPA /cygdrive/c/Users/jon/dev/tomee >> $ mvn -v >> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; >> 2018-06-17T19:33:14+01:00) >> Maven home: C:\Java\apache-maven-3.5.4 >> Java version: 1.8.0_181, vendor: Oracle Corporation, runtime: >> C:\Java\jdk8u181-b13\jre >> Default locale: en_GB, platform encoding: Cp1252 >> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" >> >> I can try different JDK versions if we think that might be a factor. >> >> Cheers >> >> Jon >> >> On Tue, Nov 27, 2018 at 7:10 AM Ferdi <d...@ferdi.id> wrote: >> >>> I've tried changing to that version as well, didn't work. >>> >>> If I run the command that broke the test: >>> >>> "C:\Program Files\Java\jdk1.8.0_161\jre\bin\java" >>> >>> -javaagent:C:\Users\Ferdi_S672\Documents\Personal\Projects\tomee\container\openejb-core\target\openejb-javaagent-8.0.0-SNAPSHOT.jar >>> >>> -Dopenejb.classloader.forced-skip=org.apache.openejb.jee.,org.apache.openejb.api. >>> -Dopenejb.classloader.forced-load=org.apache.openejb -enableassertions >>> -Dopenejb.descriptors.output.folder=./dump/ >>> -Dorg.apache.activemq.SERIALIZABLE_PACKAGES=org,java -jar >>> >>> C:\Users\FERDI_~1\AppData\Local\Temp\surefire4923413819281954940\surefirebooter7579699950053744316.jar >>> C:\Users\Ferdi_S672\AppData\Local\Temp\surefire4923413819281954940 >>> 2018-11-27T15-00-14_583-jvmRun1 surefire7936970543296277600tmp >>> surefire_04537004988640125092tmp >>> >>> I got this: >>> >>> # Created at 2018-11-27T15:08:14.729 >>> System.exit() or native command error interrupted process checker. >>> java.lang.IllegalStateException: Cannot use PPID 5228 process >>> information. Going to use NOOP events. >>> at >>> >>> org.apache.maven.surefire.booter.PpidChecker.checkProcessInfo(PpidChecker.java:155) >>> at >>> >>> org.apache.maven.surefire.booter.PpidChecker.isProcessAlive(PpidChecker.java:116) >>> at >>> org.apache.maven.surefire.booter.ForkedBooter$2.run(ForkedBooter.java:214) >>> at >>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >>> at >>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >>> at >>> >>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) >>> at >>> >>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) >>> at >>> >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) >>> at >>> >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) >>> at java.lang.Thread.run(Thread.java:748) >>> >>> On 11/26/2018 8:02 PM, Jonathan Gallimore wrote: >>>> Going to fire this off on a Linux and a Windows machine here to see a) >>> if I >>>> see the same thing, and b) see if I can give some pointers. I don't have >>>> ideas right off the top of my head at the moment. Romain's suggestion is >>>> definitely worth a try. >>>> >>>> For reference, we have a CI build here: >>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 - it doesn't >>> look >>>> like we have the same issue there (we have different ones!) >>>> >>>> Thanks for trying this - and thanks for trying it on a Windows machine >>> too, >>>> its good to know whether it is or isn't working there. >>>> >>>> Jon >>>> >>>> On Mon, Nov 26, 2018 at 7:55 AM Romain Manni-Bucau < >>> rmannibu...@gmail.com> >>>> wrote: >>>> >>>>> Hi Ferdi, >>>>> >>>>> surefire got some "hiccup" in last versions, maybe try 3.0.0-M1 or or >>>>> 2.22.1 which should work, if not the output dump can help sometimes to >>>>> identify if it is a memory issue or (more likely) another one. >>>>> >>> >>> >
