action #27409

[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 2 years ago. Updated almost 2 years ago.

Status:ResolvedStart date:06/11/2017
Priority:NormalDue date:
Assignee:EDiGiacinto% Done:

0%

Category:-
Target version:Done
Difficulty:
Duration:

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.

History

#1 Updated by szarate over 2 years ago

  • 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

#2 Updated by coolo over 2 years ago

  • Assignee set to EDiGiacinto

#3 Updated by szarate over 2 years ago

  • Target version set to Ready

This just requires testing

#5 Updated by EDiGiacinto over 2 years ago

  • Status changed from New to In Progress

#6 Updated by szarate over 2 years ago

  • 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

#7 Updated by EDiGiacinto about 2 years ago

  • Status changed from In Progress to Resolved

PRs merged

#8 Updated by szarate almost 2 years ago

  • Target version changed from Ready to Done

Also available in: Atom PDF