Project

General

Profile

Actions
Copy link

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.

Status:
Resolved
Priority:
Normal
Assignee:
EDiGiacinto
Category:
-
Target version:
Done
Start date:
2017-11-06
Due date:
% Done:

0%

Estimated time:

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.

Actions
Copy link
 #1

Updated by szarate over 6 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
Actions
Copy link
 #2

Updated by coolo over 6 years ago

  • Assignee set to EDiGiacinto
Actions
Copy link
 #3

Updated by szarate over 6 years ago

  • Target version set to Ready

This just requires testing

Actions
Copy link
 #5

Updated by EDiGiacinto over 6 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #6

Updated by szarate over 6 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
Actions
Copy link
 #7

Updated by EDiGiacinto over 6 years ago

  • Status changed from In Progress to Resolved

PRs merged

Actions
Copy link
 #8

Updated by szarate about 6 years ago

  • Target version changed from Ready to Done
Actions
Copy link

Also available in: Atom PDF