CODEWITHSUNDEEP
antcontinuous-integrationjenkinsphpunit
K-RAN
K-RAN

Reputation: 893

Jenkins ANT script fails in the middle of running

I have a bunch of PHPUnit tests that I invoke with ANT in jenkins. All of a sudden

[exec] ...............................................................  63 / 644 (  9%)
[exec] ............................................................... 126 / 644 ( 19%)
[exec] ............................................................... 189 / 644 ( 29%)
[exec] ............................................................... 252 / 644 ( 39%)
[exec] ............................................................... 315 / 644 ( 48%)
[exec] .............................................................

BUILD FAILED
/etc/jenkins/build.xml:188: exec returned: 139

Total time: 57 seconds
Build step 'Invoke Ant' marked build as failure

Funny thing is that when I manually run the tests, everything runs (at the very least) ie: goes to 100%.

I already specify Jenkins to use the ant binary from

which ant

in Jenkin's config menu and force this particular build to use it.

None of this makes sense to me because earlier today the build was succeeding. This just started to happen a few days ago and I resolved it by restarting the machine but I really want to figure out why this spontaneously happens.

Upvotes: 1

Views: 3469

Answers (2)

Walter
Walter

Reputation: 1

I also had this problem. For me it ended up in a problem with xdebug, which is needed for the codecoverage report. Loading xdebug via another php config file seemed to fix the problem.

Upvotes: 0

David W.
David W.

Reputation: 107040

Does it fail only on the Jenkins server, or does it fail on development machines too? What command is failing?

Exit code 139 is a segmentation violation. You'll have to determine what's failing.

  • Since you're using Jenkins, and your using PHP and your using <exec> why not try to do the tests outside of Ant? Jenkins can run commands as part of the build process. That will eliminate Ant as a possible cause.
  • Try playing around with <exec> settings. Setting spawn to true will spawn a subshell that won't have the memory limit that running an exec in Java would have. Running out of memory could be causing the segmentation faults.

Upvotes: 1

Related Questions