Databases
StackOverflow2013
Postsdbo
POJenkins Build Script exits after Google Test execution
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJenkins Build Script exits after Google Test execution
    primarykey
    data
    text
    <p>I am building a Qt GUI application via Jenkins. I added 3 build steps:</p> <ul> <li>Building the test executable</li> <li>Running the test executable</li> <li>compiling a coverage report with gcovr</li> </ul> <p>For some reason, the shell task for running the test executable stops after execution. Even a simple <code>echo</code> does not run after. The tests are written with Google Test and output xUnit XML files, which are analyzed after the build. Some tests start the applications user interface, so I installed the jenkins xvnc plugin to get them to run. </p> <p>The build tasks are as follows:</p> <p><strong>Build</strong></p> <pre><code>cd $WORKSPACE/projectfiles/QMake sh createbin.sh </code></pre> <p><strong>Test</strong></p> <pre><code>cd $WORKSPACE/bin ./Application --gtest_output=xml </code></pre> <p><strong>Coverage Report</strong></p> <pre><code>cd $WORKSPACE/projectfiles/QMake/out gcovr -x -o coverage.xml </code></pre> <p>Now, an <code>echo</code> at the end of the first build task is correctly printed, but an <code>echo</code> at the end of the second is not. The third build task is therefore not even run, although the Google Test output is visible. I thought that maybe the problem is that some of the Google Tests fail, but why whould the script stop executing just because the tests fail? </p> <p>Maybe someone can give me a hint on why the second task stops.</p> <p><strong>Edit</strong></p> <p>The console output looks like this:</p> <pre><code>Updating svn://repo/ to revision '2012-11-15T06:43:15.228 -0800' At revision 2053 no change for svn://repo/ since the previous build Starting xvnc [VG5] $ vncserver :10 New 'ubuntu:10 (jenkins)' desktop is ubuntu:10 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/ubuntu:10.log [VG5] $ /bin/sh -xe /tmp/hudson7777833632767565513.sh + cd /var/lib/jenkins/workspace/projectfiles/QMake + sh createbin.sh ... Compiler output ... + echo Build Done Build Done [VG5] $ /bin/sh -xe /tmp/hudson4729703161621217344.sh + cd /var/lib/jenkins/workspace/VG5/bin + ./Application --gtest_output=xml Xlib: extension "XInputExtension" missing on display ":10". [==========] Running 29 tests from 8 test cases. ... Test output ... 3 FAILED TESTS Build step 'Execute shell' marked build as failure Terminating xvnc. $ vncserver -kill :10 Killing Xvnc4 process ID 1953 Recording test results Skipping Cobertura coverage report as build was not UNSTABLE or better ... Finished: FAILURE </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdasmaze
    1. USdasmaze
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJenkins Build Script exits after Google Test execution
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJenkins Build Script exits after Google Test execution
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POJenkins Build Script exits after Google Test execution
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload