Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

Upgrading from QB 10.0.41 to QB 12.0.5 Seems to Have Broken Active Log Display #4422

tomz ·

We're testing QB 12 on our grid due to the jetty security issues, but having problems with viewing active logs.
One of our core build processes logs output to both the console window and a log file (the latter flushing periodically so not being "live" technically). In QB 10 this log displays fine while running, but in QB 12 it will only display once complete. While running it just shows a wait spinner in the log window after clicking the active log icon.

Any ideas how we can debug what is going on here? Any suggestions?
Thanks in advance.

  • replies 12
  • views 571
  • stars 0
robinshen ADMIN ·

Just tested and it works at my side. If you are running the build on an agent, please check if agent and server time is in sync.

tomz ·

It works on simple build tasks on our side (a batch script that spams echo with random data) but we do something unusual:
build batch step:

  • call ourcli.bat <- sets up a new shell
  • cli exec datatransformer <-- this runs a windows executable that it mentioned above

I will try to see if I can repro this with a more trivial build job that I can send your way. We are wondering a few things but don't have leads yet...

  • the datatransformer executable eats all CPU resources on the agent most of the time, and we're wondering if this is starving communication with the server
  • the new shell might be grabbing stderr/out in such a way where QB isn't checking children for these streams.
robinshen ADMIN ·

If it eats all CPU cycles, is it possible to lower its priority so that QB process has chance to send log to server? Also can you please test with QB11 for the same config to make sure it works?

tomz ·

It works on QB11 but the console output does appear to be garbled with ���� characters in the place of spaces. I can't say it's related, only that it still works in 11.0.33. Once the build has completed, all the weird characters display properly as spaces again. Going to try 12.0.0 next.

tomz ·

QB12.0.0 through 12.0.3 show live logs but the spaces in the log are replaced with weird unicode symbols. 12.0.4 and 12.0.5 do not start due to the SSL issue fixed in 6, and 12.0.6 will not show the live log of the process at all. Debugging in the browser shows that the JSON retrieved is truncated and corrupted (incomplete). This incomplete JSON response is constant until the build job finishes, and then the logs are viewable as normal.

robinshen ADMIN ·

Is this also happening for other jobs, or just this job? Is it possible for you to send the full log to me [robin AT pmease DOT com] for diagnostics? Log file is named as "build.log" under the build publish dir.

tomz ·

This occurs on all jobs that run one of our own specific binaries used in our build processes. It would seem that how we output to stdout/err may be causing the issue, but it is still unusual that only newer versions of QB have problems with it. I'll try to grab a reasonably sized full log today to send.

tomz ·

One of my co-workers has finally been able to trivially reproduce this issue. The problem is the "show links in log" advanced option!

You can do a for loop with an echo in batch or mass log print in powershell, (ensure you have enough time to click the active log button while it's still running). While the option is enabled, the active log will fail to output.

tomz ·
robinshen ADMIN ·

Thanks for the investigation and filing the bug. It definitely helps. Will look into the issue.

robinshen ADMIN ·
tomz ·

It appears to be resolved, thank you!