See 
<https://builds.apache.org/job/JMeter-trunk/7720/display/redirect?page=changes>

Changes:

[github] Update Darklaf: 1.4.3.1 -> 2.0.2 (#582)


------------------------------------------
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on H35 (ubuntu) in workspace 
<https://builds.apache.org/job/JMeter-trunk/ws/>
No credentials specified
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gitbox.apache.org/repos/asf/jmeter.git 
 > # timeout=10
Fetching upstream changes from https://gitbox.apache.org/repos/asf/jmeter.git
 > git --version # timeout=10
 > git fetch --tags --progress -- 
 > https://gitbox.apache.org/repos/asf/jmeter.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 35757db25078496d7877f01c1a841cc37810cb2f 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 35757db25078496d7877f01c1a841cc37810cb2f
Commit message: "Update Darklaf: 1.4.3.1 -> 2.0.2 (#582)"
 > git rev-list --no-walk 7897df534dbe8cebcb2284134fcccbc50b3b2a41 # timeout=10
Xvfb starting$ /usr/bin/Xvfb :0 -fbdir 
/home/jenkins/jenkins-slave/xvfb-7720-..fbdir578722380033925569
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
SONAR_HOST_URL=https://sonarcloud.io

[EnvInject] - Variables injected successfully.
[EnvInject] - Mask passwords that will be passed as build parameters.
[JMeter-trunk] $ /bin/bash -xe /tmp/jenkins3627113991117439687.sh
+ rm -rf src/dist/build/distributions
[Gradle] - Launching build.
[JMeter-trunk] $ <https://builds.apache.org/job/JMeter-trunk/ws/gradlew> 
"-Dorg.gradle.jvmargs=-Xmx512m -XX:MaxMetaspaceSize=512m" 
-PignoreSpotBugsFailures=true -Pspotbugs=true -PCI=true -Pcoverage=true 
--profile --no-daemon cleanTest check assemble sonarqube
To honour the JVM settings for this build a new JVM will be forked. Please 
consider using the daemon: 
https://docs.gradle.org/6.3/userguide/gradle_daemon.html.

FAILURE: Build failed with an exception.

* What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the User Manual chapter on the daemon at 
https://docs.gradle.org/6.3/userguide/gradle_daemon.html
Process command line: /usr/local/asfpackages/java/jdk1.8.0_241/bin/java 
-XX:MaxMetaspaceSize=512m -Xmx512m -Dfile.encoding=ISO-8859-1 -Duser.country=US 
-Duser.language=en -Duser.variant -cp 
/home/jenkins/.gradle/wrapper/dists/gradle-6.3-all/b4awcolw9l59x95tu1obfh9i8/gradle-6.3/lib/gradle-launcher-6.3.jar
 org.gradle.launcher.daemon.bootstrap.GradleDaemon 6.3
Please read the following process output to find out more:
-----------------------
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread


* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Xvfb stopping
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: Test reports were found 
but none of them are new. Did leafNodes run? 
For example, 
<https://builds.apache.org/job/JMeter-trunk/ws/src/components/build/test-results/test/TEST-org.apache.jmeter.assertions.CompareAssertionSpec.xml>
 is 13 days old

Reply via email to