Build failed in Jenkins: JMeter Ubuntu #941

[Apache Jenkins Server <je...@builds.apache.org>]

See <https://builds.apache.org/job/JMeter%20Ubuntu/941/display/redirect?page=changes>

Changes:

[pmouawad] build.gradle.kts : explicitely reference asm and httpcore to have the


------------------------------------------
Started by upstream project "JMeter-trunk" build number 7562
originally caused by:
 Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on H31 (ubuntu) in workspace <https://builds.apache.org/job/JMeter%20Ubuntu/ws/>
No credentials specified
Cloning the remote Git repository
Cloning repository https://gitbox.apache.org/repos/asf/jmeter.git
 > git init <https://builds.apache.org/job/JMeter%20Ubuntu/ws/> # 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 config remote.origin.url https://gitbox.apache.org/repos/asf/jmeter.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > 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 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 deef51fbede6f43ddfc16a8a2d21e38fd3ec9a97 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f deef51fbede6f43ddfc16a8a2d21e38fd3ec9a97
Commit message: "build.gradle.kts : explicitely reference asm and httpcore to have the correct version used in generated pom"
 > git rev-list --no-walk 4d9731c92cfc4b2695be5eceb1a9d1569b7a3933 # timeout=10
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
Injecting SonarQube environment variables using the configuration: ASF Sonar Analysis
[Gradle] - Launching build.
[JMeter Ubuntu] $ "<https://builds.apache.org/job/JMeter%20Ubuntu/ws/gradlew"> -Djava.awt.headless=true -PCI=true --stacktrace check createDist
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
WARN: Unable to locate 'report-task.txt' in the workspace. Did the SonarScanner succeeded?
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released

Jenkins build is back to normal : JMeter Ubuntu #942

[Apache Jenkins Server <je...@builds.apache.org>]

See <https://builds.apache.org/job/JMeter%20Ubuntu/942/display/redirect?page=changes>