beam-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Jenkins Server <>
Subject Build failed in Jenkins: beam_PostRelease_NightlySnapshot #564
Date Mon, 25 Mar 2019 20:48:49 GMT
See <>

GitHub pull request #8132 of commit b33aad21c06ed5454760e09503b4f01b316f5551, no merge conflicts.
Setting status of b33aad21c06ed5454760e09503b4f01b316f5551 to PENDING with url
and message: 'Build started for merge commit.'
Using context: ./gradlew :release:runJavaExamplesValidationTask
[EnvInject] - Loading node environment variables.
Building remotely on beam8 (beam) in 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/*
 > git rev-parse refs/remotes/origin/pr/8132/merge^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/pr/8132/merge^{commit} # timeout=10
Checking out Revision 0d2be31acebb43f5382e4d88eff5fdf70dc7aef8 (refs/remotes/origin/pr/8132/merge)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0d2be31acebb43f5382e4d88eff5fdf70dc7aef8
Commit message: "Merge b33aad21c06ed5454760e09503b4f01b316f5551 into 43db80deca44273716c500520439aaa4e48688b4"
First time build. Skipping changelog.
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - Injecting as environment variables the properties content 

[EnvInject] - Variables injected successfully.
[Gradle] - Launching build.
[src] $ <>
--continue --max-workers=12 -Dorg.gradle.jvmargs=-Xms2g -Dorg.gradle.jvmargs=-Xmx4g -Pver=
-Prepourl= :release:runJavaExamplesValidationTask
To honour the JVM settings for this build a new JVM will be forked. Please consider using
the daemon:

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
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
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message