Ticket #189 (new defect)

Opened 6 months ago

Last modified 1 week ago

phingcall does return build failed correctly

Reported by: anonymous Assigned to: hans
Priority: major Milestone: 2.3.1
Component: phing-core Version: 2.3.0
Keywords: Cc:

Description

When trying to group several (test) tasks into one task using phingcall then failures in called targets are ignored in the main task. When a subtask fails the build still finished successfully.

Attachments

Change History

03/21/08 09:38:12 changed by hans

I'm not sure what the expected behavior would be here. Should the entire build fail immediately if one of the foreach loops fails? Or should it only fail the build after the foreach has been run?

05/06/08 20:36:16 changed by jason.mcclellan@ca.com

I would expect that if a target I call using phingcall fails then the entire build would fail.

In my current setup, for example, I have to run my unit tests via phingcall because if run within the current instance of phing I get session errors because of output already having been started previously in the build. So, if I fork with phingcall this solves the problem. However, if my tests fail, I still want the build to fail.

Is there some way this could be an option for phingcall?

Add/Change #189 (phingcall does return build failed correctly)