Compass Version1.1

Build Output

The build output section on the build results page shows the script output of every build step as well as the reported result of each build step.  This section looks like this:

In the above example the build plan has 3 bild steps each of which reported no failures and completed successfully.  The name of each build step is displayed on the left and when clicked, expands the build output section to show all of the output from the build step.  Here is an example of what the build output window looks like when one of the sections is expanded:

When the client_test build step was clicked it expanded to show the build step output box.  The build step output box shows a box with at the top with exactly the command line that was executed followed by all output, both standard output and error output, that the script generated when it executed.  In the above case, we see a PyUnit test that executed 11 test cases and they all passed.  

There are four status values that are possible for each build step:

PASSED

The PASSED status value indicates that the script ran and that no exceptions were thrown and the error status when the script exited was normal. As you can see in the above screen shots, PASSED build steps are colored green.

FAILED

The FAILED status value occurs when one of three conditions is met. 

1. The script exited with an error code
2. An exception was thrown in the script that was not caught
3. The build step was configured to use a unit test parser and one of the unit tests failed, or the parser returned an error

When a build step reports a status of FAILED, Compass halts execution on the build run and reports the build run as a failure. This is what a FAILED build step looks like in the build output section:

In this case the repository check out script failed.  If we expand the checkout script and scroll to the bottom of the output we see:

It may look like there is nothing wrong since the last line in the output does not seem to indicate there was an error.  But, if we look a few lines up from the bottom we see this:

In this case, the build step failed because the subversion repository lost its connection to the server.  The reason the error is not at the bottom of the output is that subversion reports errors on std::error, but outputs its status on std::output.  Compass collects these two outputs through a combined output stream and sometimes this results in a slight reordering of output.  When observing error output, it is important to realize that the output may be out of order with respect to standard output.

WARNING

The WARNING status value indicates that the script reported a failure just like for the FAILED case above and normally this would result in reporting a status of FAILED.  However the build step was configured to treat errors as warnings and to continue executing the build plan and so a status of WARNING was issued instead.  This is convenient for unit tests, where even if a unit test fails we still want all the other unit test build steps to execute.  A warning build step looks like this:

In the above screen shot a unit test failed but the 'buildstest' build step was set up to issue a warning and continue if an error was detected.  

PENDING

When a build run is currently running on a client it reports back results after every build step and if a build step takes longer than 1 minute, the build client will report back to the Compass server any output it has recieved thus far.  During long compilations or during large checkouts, users can check the build status page to see the current state of the build client.  An example of what this looks like is shown below: