URGENT: ESAPI on MacOS with JDK 7 failing tests

18 views
Skip to first unread message

Kevin W. Wall

unread,
Mar 22, 2021, 8:49:46 PM3/22/21
to esapi-project-users, esapi-project-dev, Dave Wichers
Dave Wichers informs me that the latest version of ESAPI in the 'develop' branch is failing on a lot of tests when executed on MacOS using Java 7. (And oddly, it is only attempting to execute 2079 of the tests rather than 4316 of them as it does with JDK 7 on Linux; haven't tried JDK 7 recently under Windows.) We are aware of SecurityProviderLoaderTest.testWithBouncyCastle() failing under that scenario; that's already been documented in previous release notes.

Anyhow, I'm not sure if this is something that I want to hold up the 2.2.3.0 release for unless someone else on one of these 2 lists says "I absolutely need that" as in this would be a showstopper for you. So speak up now or forever hold your peas (and carrots and broccoli and whatever other vegetables you want to insert here).

If we decide to hold it up until this is resolved, it may take a while because I don't own a Mac to test it on and I'm not sure if Matt or Jeremiah do either.

Thanks,
-kevin
--
Blog: https://off-the-wall-security.blogspot.com/    | Twitter: @KevinWWall | OWASP ESAPI Project co-lead
NSA: All your crypto bit are belong to us.

Matt Seil

unread,
Mar 22, 2021, 11:18:40 PM3/22/21
to Kevin W. Wall, esapi-project-users, esapi-project-dev, Dave Wichers

I do not. 

--
You received this message because you are subscribed to the Google Groups "ESAPI Project Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to esapi-project-u...@owasp.org.
To view this discussion on the web visit https://groups.google.com/a/owasp.org/d/msgid/esapi-project-users/CAOPE6PjyLbQtdgNvV7yh8MhCpKYWGnfpAOQqrVbYy%2B5%2BDoKmwQ%40mail.gmail.com.

Nate Chadwick

unread,
Mar 23, 2021, 10:28:16 AM3/23/21
to Matt Seil, Kevin W. Wall, esapi-project-users, esapi-project-dev, Dave Wichers
It looks like on 1.7 just need to increase xmx / permgensize

On develop branch on Mac with 1.8 - mvn test=>

[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 s - in org.owasp.esapi.reference.validation.StringValidationRuleTest

[INFO] 

[INFO] Results:

[INFO] 

[INFO] Tests run: 4316, Failures: 0, Errors: 0, Skipped: 0

[INFO] 

[INFO] ------------------------------------------------------------------------

[INFO] BUILD SUCCESS

[INFO] ------------------------------------------------------------------------

[INFO] Total time:  39.565 s

[INFO] Finished at: 2021-03-23T10:00:01-04:00

[INFO] ------------------------------------------------------------------------


On 1.7 on mac:  mvn test

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M2:test (default-test) on project esapi: There are test failures.

[ERROR] 

[ERROR] Please refer to /Users/natechadwick/DevEnv/esapi-java-legacy/target/surefire-reports for the individual test results.

[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.

[ERROR] The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ERROR] Command was /bin/sh -c cd /Users/natechadwick/DevEnv/esapi-java-legacy && /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/bin/java -jar /Users/natechadwick/DevEnv/esapi-java-legacy/target/surefire/surefirebooter8164811408990302845.jar /Users/natechadwick/DevEnv/esapi-java-legacy/target/surefire 2021-03-23T10-21-15_263-jvmRun1 surefire5911722560280391625tmp surefire_04534118398768350926tmp

[ERROR] Error occurred in starting fork, check output in log

[ERROR] Process Exit Code: 1

[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ERROR] Command was /bin/sh -c cd /Users/natechadwick/DevEnv/esapi-java-legacy && /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/bin/java -jar /Users/natechadwick/DevEnv/esapi-java-legacy/target/surefire/surefirebooter8164811408990302845.jar /Users/natechadwick/DevEnv/esapi-java-legacy/target/surefire 2021-03-23T10-21-15_263-jvmRun1 surefire5911722560280391625tmp surefire_04534118398768350926tmp

[ERROR] Error occurred in starting fork, check output in log

[ERROR] Process Exit Code: 1

[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:670)

[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:283)

[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:246)

[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1159)

[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1000)

[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:846)

[ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)

[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)

[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)

[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)

[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)

[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)

[ERROR] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)

[ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)

[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)

[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)

[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)

[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)

[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)

[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

[ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

[ERROR] at java.lang.reflect.Method.invoke(Method.java:606)

[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)

[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)

[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)

[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)

[ERROR] 

[ERROR] -> [Help 1]

[ERROR] 

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


Adding memory seems to resolve it:

1.7 on mac: mvn test -DargLine="-Xmx20484m -XX:MaxPermSize=256m"

[INFO] Results:

[INFO] 

[INFO] Tests run: 4316, Failures: 0, Errors: 0, Skipped: 0

[INFO] 

[INFO] ------------------------------------------------------------------------

[INFO] BUILD SUCCESS

[INFO] ------------------------------------------------------------------------

[INFO] Total time:  40.987 s

[INFO] Finished at: 2021-03-23T10:23:58-04:00

[INFO] ------------------------------------------------------------------------



--
Nate Chadwick • Vice President of Products & Services
(0) 781-835-1356 |  (M) 781-835-8766 | nate_c...@percussion.com 
100 Summit Drive, Suite 100 | Burlington, MA 01803 | www.percussion.com

Follow us on Twitter @percussion


Reply all
Reply to author
Forward
0 new messages