Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Gradle build fails randomly

See original GitHub issue

Description

When building our react native app on our jenkins, the build sometimes just fails. It does that pretty randomly.

This is the log output from the build:

Starting process 'command 'node''. Working directory: /home/jenkins/workspace/ Command: node node_modules/react-native/local-cli/cli.js bundle --platform android --dev false --reset-cache --entry-file index.android.js --bundle-output /home/jenkins/workspace/android/app/build/intermediates/assets/release/index.android.bundle --assets-dest /home/jenkins/workspace/android/app/build/intermediates/res/merged/release
Successfully started process 'command 'node''
Scanning 605 folders for symlinks in /home/jenkins/workspace/node_modules (4ms)
Scanning 605 folders for symlinks in /home/jenkins/workspace/node_modules (4ms)
Loading dependency graph, done.
warning: the transform cache was reset.
# :app:bundleReleaseJsAndAssets FAILED
:app:bundleReleaseJsAndAssets (Thread[main,5,main]) completed. Took 2 mins 38.439 secs.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:bundleReleaseJsAndAssets'.
> Process 'command 'node'' finished with non-zero exit value 137
* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output.
BUILD FAILED
Total time: 4 mins 18.872 secs
Stopped 0 compiler daemon(s).
script returned exit code 1

Reproduction Steps and Sample Code

./gradlew clean assembleRelease

Additional Information

React Native version: 0.42.3
Platform: Android
Development Operating System: Debian GNU/Linux 8 (jessie)
Dev tools: Android Build Tools 25.0.2, Node v7.7.3, NPM 4.1.2, Gradle 2.14.1

Issue Analytics

State:
Created 6 years ago
Reactions:6
Comments:7 (1 by maintainers)

Top GitHub Comments

2reactions

jniebuhrcommented, May 10, 2017

Exit Code 137 basically means the underlying process has been killed with Signal 9, so a SIGKILL.

0reactions

DylanVanncommented, May 4, 2018

I wonder if doing react-native start as a separate command in parallel on CI might help with some of these errors.

Top Results From Across the Web

Random gradle build failures when run migration tests #1355

When we turn on the db schema migration test, we got the random gralde build failure: Caused by: java.lang.AssertionError: com.intellij.lang ...

gradle build consistently fails at download of random plugin

For two days now, I have the problem, that my gradle builds fail (pretty consistently, today only one in 15 succeeded) when downloading...

Random failures with Gradle delete, processResources or ...

We are slowly rolling out Gradle in our enterprise and many devs with Macs are reporting random build failures specially during delete, processResources...

Gradle failing randomly (#2146) · Issues - GitLab

It's happening randomly on different stages and jobs. I don't cache files because for me, it is taking too much space and builds...

gradle build fails inconsistently : IDEA-260181 - YouTrack

gradle build fails inconsistently · Run the "clean" task by double clicking it in the gradle tool window · Stop IDEA's gradle daemon:...