|
|
|
[
Permlink
| « Hide
]
Robin Shen [05/Jun/19 11:46 PM]
Thanks reporting. Will investigate the issue.
Can you please send backup of your database (can be taken from QB admin page) and let me know the build and step to check?
Backup can be sent to [robin AT pmease DOT com]
Builds to look at:
https://automation.pfsweb.com:8810/build/19747626 https://automation.pfsweb.com:8810/build/19781143 The job is one parallel composition with multiple steps all doing the same thing on different boxes. As a vendor outside of your company, I can not access your internal server.
Thanks for sending the backup. I restored it successfully now. For the failed build log, please let me know the corresponding build id, also please check the option "show steps" when download the build log.
Build logs re attached with build ids referenced
Second build has rolled out of history (More then 30days) but I have re downloaded the build log for 19781143 with show steps
Thanks for sending the log. Checked carefully with code but still can not find the reason. Is it possible that you upgrade to QB9 which has additional debug logging for this issue? It can be downloaded from:
https://build.pmease.com/build/4898 After upgrading to this version, please edit general setting of the configuration in question to use debug logging, then reproduce the issue to send build log (still with "show steps" option ticked). Just to let you know that we have the exact same issue.
Already discussed on the forum here https://support.pmease.com/PMEase/QuickBuild/topics/3996/steps-executed-even-if-previous-one-is-failed?1 and by email with Robin. We're using QB 8.20 but we can't upgrade to QB 9.0 for the moment. We have no idea why and when this happens and it's really a pain :( "Happy" to see that we're not alone and I hope a fix we'll be found soon. I have the same issue and I'm running QB9.0.11
Hi,
Can you increase the priority of this issue. It's very time consuming for us and we don't have any workaround. Our only hope was to upgrade to QB 9, but if it don't fix it.... We are working with a MariaDB database. I don't think it the root cause, but may be. @Dennis Morand, what DB are you using ? It's probably a concurrency issue while reserving resources. Thanks, Rafael According to several reports here, it seems that this issue occurs when the step is being enclosed in a parallel container step. Is that right? If so, have you specified the concurrent workers in advanced settings of the parallel step?
Upgrading to QB9 will not solve the issue, but will give us more clue when the issue happens. After upgrading to QB9, please modify "conf/log4j.properties" on the agent running PARENT step of the duplicating step to add below line: log4j.logger.com.pmease.quickbuild.grid.GridImpl=DEBUG When the issue happens, please send me the agent log on that node. Indeed, in our cases the problem always happens in parallel steps.
The number of workers is set to 0. We never used this feature till now.
Finally get this issue solved in 9.0.39:
https://build.pmease.com/build/5118 Sorry for taking so long time. Hurrah!
I didn't think anymore this would ever happen. Thanks for that fix ! But now we have to upgrade ... :) |