Details
-
Type:
Story
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Bamboo
-
Labels:None
Description
First noticed with the Legacy jalview develop build. Builds were completing as normal, but were reporting 'no tests' - even though there was testng test output present in the log, and stages appeared to have executed successfully.
It turned out that the ant-x11 script, which uses xvfb-run under the hood, was terminating with EXIT_FAILURE and a message on stderr:
build 04-Sep-2019 14:28:50 BUILD SUCCESSFUL
build 04-Sep-2019 14:28:50 Total time: 4 minutes 3 seconds
error 04-Sep-2019 14:28:50 /usr/bin/xvfb-run: line 186: kill: (30856) - No such process
simple 04-Sep-2019 14:28:50 Failing task since return code of [/home/bamboo/buildtools/x11-ant/bin/ant -Djava.io.tmpdir=/home/bamboo/latest/temp/JB-JDB178-JOB1 -f build.xml -Dclover.jar=/home/bamboo/buildtools/clover/lib/clover.jar clean with.clover testng clover.report] was 1 while expected 0
The fix here was to move the 'process TestNG results' stage of the job to the 'always execute' section of the job, so processing occurs regardless of the return code of the ant-x11 testng step.
It turned out that the ant-x11 script, which uses xvfb-run under the hood, was terminating with EXIT_FAILURE and a message on stderr:
build 04-Sep-2019 14:28:50 BUILD SUCCESSFUL
build 04-Sep-2019 14:28:50 Total time: 4 minutes 3 seconds
error 04-Sep-2019 14:28:50 /usr/bin/xvfb-run: line 186: kill: (30856) - No such process
simple 04-Sep-2019 14:28:50 Failing task since return code of [/home/bamboo/buildtools/x11-ant/bin/ant -Djava.io.tmpdir=/home/bamboo/latest/temp/JB-JDB178-JOB1 -f build.xml -Dclover.jar=/home/bamboo/buildtools/clover/lib/clover.jar clean with.clover testng clover.report] was 1 while expected 0
The fix here was to move the 'process TestNG results' stage of the job to the 'always execute' section of the job, so processing occurs regardless of the return code of the ant-x11 testng step.