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.

Live build log stays blank? #2387

Productivity ·
Hello,

I noticed that sometimes, the live build log is blank (i.e. empty) when I check the log for a running build. So I created a build configuration in order to reproduce this bug and to narrow down the factors that trigger this bug, here are my findings:

Configuration details
Build steps: Only 1 build step, which is to checkout a big project (~5 GB)
Build log level: Debug

When running on a Windows node, I can see the build log being updated live every 5 seconds to display which files are being checked out. But on a Linux node, for the same configuration, the live build log screen remains empty until the check out is finished.

Do you have an idea why? I'm using QB 5.0.25.

Thanks!
  • replies 15
  • views 3788
  • stars 0
robinshen ADMIN ·
What is your SCM tool used for checking out? And in case of Linux, is Linux machine connected to QB server as an agent, or is it a QB server itself?
Productivity ·
I use SVN as our SCM tool. Both the Windows and Linux machine on which I tested this are build agents that are not QB servers.
robinshen ADMIN ·
Looks like the problem is caused by the factor that your linux agent's system time is not in sync with QB server.
Productivity ·
Looking at my Linux node (running Ubuntu) compared to my QB server (running Windows Server 2008), the Linux node's system time is maybe 1 minute ahead of the QB server.

Is that still too much? And I don't understand the impact of the system time on the live build log, could you explain why it would affect the live build log?
robinshen ADMIN ·
When send live logs, QB server collects from all build agents live log entries in a certain time range and send back to browser. The time window is 5 seconds, and this window will move forward for every request to make the log live, so the time sync with server matters. We uses server time as time window instead of using time of all agents hoping to reduce the traffic to the minimum.
jossy ·
We also experiencing this problem and the gap between server time and node time is about a couple of seconds, but sometimes the log is never updated and also the step overview only shows the master step running. After the build is finished everything is available (logs, step details, etc.). As this occurs on QB 4.0.92 maybe this is already solved in QB 5, but if not wouldn't it be possible to determine the gap between server and node when a build starts and consider this gap while the build is running. I think the traffic overhead would be very low.

Also also checked the times again and the gap is about 10 seconds.

Thanks
robinshen ADMIN ·
In latest QB 5.1 version (actually fixed since 5.1.15) we've optimized the live log logic to make it working even if time of agent and server is not in sync. Please do an upgrade to see if it fixes the problem.
jossy ·
Now we have 5.1.18 installed and still experience that sometimes the live log stays blank and also the build seems to "hang" in master step.
robinshen ADMIN ·
Will it hang there forever? Does the master step perform some heavy tasks in pre-execute/post-execute step?
jossy ·
It will not "hang" forever. After some time when the build is done everything appears to be fine. Pre-Execute in Master doesn't do heavy tasks.
robinshen ADMIN ·
Are you able to reproduce this issue with some set ups so that I can try at my side?
jossy ·
I do not know what the problem is, or how to reproduce it.

I filed an issue with some screenshots: http://track.pmease.com/browse/QB-2013

I hope you find the cause of this problem, I wasn't able to reproduce this with some setup. It occurs on random nodes.

Thanks
vanderhu ·
I am also noticing similar behaviour with 5.1.16 version, namely following entries I found in the agent log. Not sure if it is related or something different:

2014-04-06 05:52:52,420 [DefaultQuartzScheduler_Worker-43] INFO com.pmease.quickbuild.log.DefaultLivelogManager - Removing obsolete live log entries of build: 1935231
2014-04-06 05:53:32,160 [pool-1-thread-179] INFO com.pmease.quickbuild.CheckConditionJob - Taking repository snapshots...
2014-04-06 05:58:02,286 [DefaultQuartzScheduler_Worker-44] INFO com.pmease.quickbuild.log.DefaultLivelogManager - Removing obsolete live log entries of build: 1935231
robinshen ADMIN ·
This entry means that QB removes obsolete live log entries after some time and should not cause this issue. Will check the issue...
vanderhu ·
I am seeing this logs in agent log always when I have as well a empty/blank live log. Checked system time from agent and server and they seem to be in sync. So it could well be related somehow in my opinion.