| Key: |
QB-3115
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Robin Shen
|
| Reporter: |
AlSt
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 09/Jan/18 02:08 PM
Updated: 24/Feb/18 03:19 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
7.0.30
|
| Fix Version/s: |
8.0.0
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
When the max workers setting is set and one of the child steps is failing then the remaining pending child steps get skipped.
This might make sense in some cases, but in our case we want to test on different platforms and see which ones fail.
So something like a "continue" flag would be nice to have all child steps executed even when one of the other steps fail.
This is the case when no max workers are defined. All child steps are executed and none are skipped.
As I said: The fail early approach might really make sense in some cases, but not in our case. At least for a lot of test configurations/builds.
|
|
Description
|
When the max workers setting is set and one of the child steps is failing then the remaining pending child steps get skipped.
This might make sense in some cases, but in our case we want to test on different platforms and see which ones fail.
So something like a "continue" flag would be nice to have all child steps executed even when one of the other steps fail.
This is the case when no max workers are defined. All child steps are executed and none are skipped.
As I said: The fail early approach might really make sense in some cases, but not in our case. At least for a lot of test configurations/builds. |
Show » |
|
When max workers are set in parallel composite step and one fails the pending steps are skipped.