action #27409
closed
[tools][sprint 201711.2] Make an option for barriers to get destroyed if one of the jobs belonging to it fails
Added by EDiGiacinto over 6 years ago.
Updated about 6 years ago.
Description
This was discussed with Martin since it's forcing complex tests logics in Caasp tests to cover situations were it would be easier to have the barrier destroyed in case one of the jobs belonging to it fails - otherway the remaining job will be waiting for the barrier until job timeout is reached.
- Subject changed from [tools] Make an option for barriers to get destroyed if one of the jobs belonging to it fails to [tools][Sprint 201711.01] Make an option for barriers to get destroyed if one of the jobs belonging to it fails
- Assignee set to EDiGiacinto
- Target version set to Ready
This just requires testing
- Status changed from New to In Progress
- Subject changed from [tools][Sprint 201711.01] Make an option for barriers to get destroyed if one of the jobs belonging to it fails to [tools][sprint 201711.2] Make an option for barriers to get destroyed if one of the jobs belonging to it fails
- Status changed from In Progress to Resolved
- Target version changed from Ready to Done
Also available in: Atom
PDF