| << Back to previous view |
|
[QB-952] Please give access to logs for completed steps of cancelled builds
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 4.0.0-M1 |
| Fix Version/s: | 4.0.0-M2 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Don Ross | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
I have a build which takes about a half-hour to run on Windows, and five minutes on MacOS.
I am running it as a parallel composition build step, one sub-step run on each platform. If the Mac OS build fails, I have to wait for the Windows build to complete before I can see the results of the failed Mac step. I would like to just cancel the build and look at what has completed so far. However, if I cancel the build, all that ends up in the log is the cancellation message. |
| Comments |
| Comment by Robin Shen [ 15/Jun/11 11:37 PM ] |
| Please edit both steps and click the advanced setting, you will see a post execute action there. Just specify it as "Cancel sibling steps if current is failed". Then other steps will be cancelled if one step fails, and you will be able to see the whole build log. |
| Comment by Don Ross [ 22/Jul/11 09:58 PM ] |
|
So, I finally got around to trying this, and it doesn't work. The sibling steps keep on running after the failed step ends.
Is it possible this only works if the steps are on the same system? |
| Comment by Robin Shen [ 22/Jul/11 11:23 PM ] |
| Which version are you using? |
| Comment by Don Ross [ 29/Jul/11 02:52 PM ] |
|
We are using 4.0.0-M1, 2011-07-02.
I just re-ran the test, and it just so happened that two of my steps were both on the same system. One queued for the other... the first one failed in under a minute, and then the second one ran on the same system (and also failed). Meanwhile, the other parallel steps (there were six in total) continued to run on other systems for another five minutes. This in spite of having the 'cancel sibling steps' option. |
| Comment by Robin Shen [ 29/Jul/11 11:36 PM ] |
| What do you mean by one queued for the other? Are all these parallel steps triggering other builds? |
| Comment by Don Ross [ 03/Aug/11 03:15 PM ] |
|
No, no... I mean... Hmm, hard to describe.
I am triggering two steps in parallel. Due to the vagarities of the system, they both were assigned to the same host. Due to workspace locking, only one can execute at a time. So, the first one failed, and then the second one started on the same host, and also failed. Since 'cancel sibling steps' was enabled, I would have expected the second step to be cancelled when the first one failed. Can we re-open this ticket since it is not fixed yet? |
| Comment by Robin Shen [ 04/Aug/11 01:56 AM ] |
| Verified this is a re-introduced bug of 4.0 M1. Will get it fixed in M2. |