History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CIB-1385
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: jason
Reporter: James French
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pulse

Unexpected failure state/message

Created: 21/Feb/08 04:08 PM   Updated: 04/Apr/08 12:36 PM
Component/s: Build core
Affects Version/s: 1.2.46
Fix Version/s: 2.0.5, 1.2.50


 Description  « Hide
This is not a huge deal but I thought it worthy of reporting.

I just got a situation where I just checked in a large merge and I had to leave some conlicts in for someone else to solve. Pulse then built the project and the build failed, as expected. However the manner in which it failed is to my mind wrong.

What happened was that compilation failed which caused the command that launched my build script to fail. I would expect the build to stop there and the result by reported as a 'failure'. But what happened is that pulse carried on and tried to gather artifacts that didn't exist - the end state was therefore 'error' with a message about not finding artifacts.

One upshot of this type of behaviour is that people that are subscribed to builds with the condition 'failure and changed.by.me' don't get an email when they should (which is how everyone is set up here). Another upshot is that the message is misleading and is hiding the real problem.

As I said, not a huge deal at all, but my perfectionism wouldn't let me not report it :)


 All   Comments   Change History      Sort Order:
jason - 21/Feb/08 06:53 PM
Hi James,

Thanks for the report: it is certainly worthy of fixing. For now you may be able to work around it by setting the fail-if-not-present flag on your artifacts to false, although obviously that will have the effect of hiding problems with your artifacts not being generated.

jason - 03/Apr/08 11:42 PM
Fixed in change 4255.

James French - 04/Apr/08 10:36 AM
Yay! Cheers Jason.

jason - 04/Apr/08 12:34 PM
Merged to trunk in change 4262.

jason - 04/Apr/08 12:36 PM
No problem James. I will be releasing the build with the fix (1.2.50) today. The fix means artifact collection will still go ahead (some may be there to capture), but failure to collect artifacts is silent if the command has already failed (as the cause is likely to be the command failure).