jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Jenkins Server <>
Subject Build failed in Jenkins: JMeter » JMeter-trunk #88
Date Wed, 16 Sep 2020 21:05:01 GMT
See <>


[Vladimir Sitnikov] Return empty string instead of null in #getToolTipText(MouseEvent) for
main frame tree.

Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on H40 (ubuntu) in workspace <>
[WS-CLEANUP] Deleting project workspace...
No credentials specified
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url # timeout=10
Fetching upstream changes from
 > git --version # timeout=10
 > git fetch --tags --progress -- +refs/heads/*:refs/remotes/origin/*
# timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision e33cd1898626b831d8f25304bb80341111ffe892 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e33cd1898626b831d8f25304bb80341111ffe892 # timeout=10
Commit message: "Return empty string instead of null in #getToolTipText(MouseEvent) for main
frame tree."
 > git rev-list --no-walk 0eff2c5a6c0bcfd17ac62a5ef3d99aeb78101eeb # timeout=10
Xvfb starting$ /usr/bin/Xvfb :0 -fbdir /home/jenkins/jenkins-agent/xvfb-88-..fbdir5209042183302688937
[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - Injecting as environment variables the properties content 

[EnvInject] - Variables injected successfully.
[EnvInject] - Mask passwords that will be passed as build parameters.
[Gradle] - Launching build.
[JMeter-trunk] $ <>
"-Dorg.gradle.jvmargs=-Xmx512m -XX:MaxMetaspaceSize=512m" -PignoreSpotBugsFailures=true -Pspotbugs=true
-PCI=true -Pcoverage=true --profile --no-daemon cleanTest check assemble
To honour the JVM settings for this build a new JVM will be forked. Please consider using
the daemon:
Daemon will be stopped at the end of the build stopping after processing

FAILURE: Build failed with an exception.

* What went wrong:
Gradle could not start your build.
> Could not create service of type FileAccessTimeJournal using GradleUserHomeScopeServices.createFileAccessTimeJournal().
   > Timeout waiting to lock journal cache (/home/jenkins/.gradle/caches/journal-1). It
is currently in use by another Gradle instance.
     Owner PID: 13319
     Our PID: 16316
     Owner Operation: 
     Our operation: 
     Lock file: /home/jenkins/.gradle/caches/journal-1/journal-1.lock

* 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

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, <>
is 2 days 11 hr old

View raw message