[#CIB-1198] Build status shows as "in progress" even though the build is completed.

Pulse

Build status shows as "in progress" even though the build is completed.

Created: 13/Aug/07 05:05 PM Updated: 18/Aug/07 05:25 AM

Component/s:

Web UI

Affects Version/s:

1.2.34

Fix Version/s:

1.2.35

File Attachments:

build-output.zip (189 kb)
2.

logs.tar.gz (162 kb)

Description

« Hide

We have a build listed in the history of one of our projects that still shows "in progress". This build appears to be completed successfully and has artifacts and logs available, but the status is stuck incorrectly.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

jason - 14/Aug/07 07:05 AM

Hi Matt,

I am guessing that you logs may indicate what caused this build to become stuck. If you could zip them and mail them to support@zutubi.com that would be much appreciated. Also, a Pulse restart (when convenient) should "unstick" the build.

[ Permlink | « Hide ]

Matt Spaulding - 14/Aug/07 03:57 PM

Here's the collection of build output from one of our stuck builds.

[ Permlink | « Hide ]

jason - 14/Aug/07 09:18 PM

Hi Matt,

Thanks for the info, but unfortunately I should have been more specific, my apologies. I was referring to the server logs from $PULSE_HOME/logs directory. rather than the build logs. I expect an error may have been recorded for this build.

[ Permlink | « Hide ]

jason - 15/Aug/07 07:27 AM

Note that this is possibly a manifestation of ~~CIB-1206~~.

[ Permlink | « Hide ]

Matt Spaulding - 16/Aug/07 04:47 PM

Here are the Pulse logs from $PULSE_HOME/logs

[ Permlink | « Hide ]

Matt Spaulding - 16/Aug/07 04:48 PM

We've also experienced another very similar problem with the build status. Some builds have generated errors. Pulse recognizes that the build failed and shows the errors under the "features" heading, but the build status shows that it was a "pass".

[ Permlink | « Hide ]

jason - 18/Aug/07 05:25 AM

Hi Matt,

Thanks for the logs. This indeed looks like another case of ~~CIB-1206~~. Regarding a build with error messages succeeding, this may be due to post-processor configuration. For the most part Pulse will use command exit codes as the most reliable way to tell if a build succeeded. This means that even though a post-processor picks up what it believes is an error, the build may pass. In most cases it is possible to configure this behaviour using the fail-on-error attribute common to most post-processors. It may also be worth checking that the build commands exit with the correct code (something non-zero) on error. If you look into this and it still appears that Pulse is at fault, please raise a bug with the error messages you are getting.