| << Back to previous view |
|
[QB-2099] Build overview is empty when it should show sub running steps
|
|
| Status: | Open |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Jonathan T-Delorme | Assigned To: | Robin Shen |
| Resolution: | Unresolved | Votes: | 1 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| File Attachments: |
screenshot-1.jpg
screenshot-2.jpg
Steps_disappearing_From_Web_2014-06-23_1027.swf
|
| Description |
|
Normally when we run our build, the "Overview" page shows sub running steps. But now, it shows an empty page.
As well when I try to question it via the REST api, I get no "Runtime steps" informations in the returned XML |
| Comments |
| Comment by Jonathan T-Delorme [ 20/Jun/14 01:24 PM ] |
| Overview page without any information until the build finishes |
| Comment by Jonathan T-Delorme [ 20/Jun/14 01:25 PM ] |
| What I see normally after the build finishes |
| Comment by Robin Shen [ 21/Jun/14 12:22 AM ] |
| Does child steps being able to be displayed while build is running if you manually refresh the page? Or if you have some reproducing steps for this issue, it will be a lot easier for us to get it solved. |
| Comment by Jonathan T-Delorme [ 23/Jun/14 08:30 AM ] |
|
Here is a visual of what is happening:
I use a "Schedule other build step". |
| Comment by Jonathan T-Delorme [ 23/Jun/14 02:11 PM ] |
|
I found a workaround, I think it has to do with the master step using the same machine as a child step (even if they use the same workspace)
If I force the master step to run on another machine, the steps does not disappear. |
| Comment by Robin Shen [ 23/Jun/14 11:09 PM ] |
| The build overview page should show child steps even if they run on same machine or use same workspace. If you are able to reproduce this issue, let me know the steps will be of a lot help. |
| Comment by Jonathan T-Delorme [ 24/Jun/14 03:18 PM ] |
|
Hi Robin,
I don't have easy repro steps. Globally, I created a master step that triggers child configurations using a repeat parameters. I wait about 10 seconds and the currently running info disappears (as seen in the attached video). I feel like when a child step is started using the same machine, the "runtime steps" are not updated anymore. Since I now have a workaround, the issue is not so important for now. Thanks for your support |
| Comment by Robin Shen [ 25/Jun/14 12:17 AM ] |
| Thanks for the info. We will also check it at our side to see if we can find anything. |