Render time in Chrome/Firefox

Hi Pat,

I recently noticed that we weren’t getting render time data from our Chrome and Firefox agents in our private WPT instance. I just upgraded to 2.11, and the agents should have updated themselves as well:


You can see an example test result here with a 0.000s Start Render:


Is this a known issue, or something that’s easy to fix? The WPT box and the agents are all on EC2 using the AMIs that you provide. Thanks!


Hmm, that’s quite strange. Looks like the desktop is locked but that shouldn’t happen on the EC2 images. The start render times are messed up because of whatever is causing the black screen shots. Did anyone RDP to the machines by any chance? If so they you need to reboot them instead of disconnecting.

btw, I removed the IP address and used the “publish to” to post your test to the public instance for sharing (just so you don’t get people abusing your private instance in case it’s not locked down):

Thanks for removing the IP address - good call.

I just RDPed to the test agent and rebooted it, and it looks like things are working now! I guess someone logged in and didn’t reboot afterwards. I’ll add “reboot test agents” to my list of debugging steps prior to posting ;-).