UI timing test fails on startup timings

[sshane]

Either move the blocking vipc recv into a thread like Qt (complex), or detect that this is the source properly in the test

https://jenkins.comma.life/blue/organizations/jenkins/openpilot/detail/master/332/pipeline

[deanlee]

The primary factor affecting startup time isn't the VisionIPC , as its connection and receive operations are handled non-blockingly within the rendering loop (after being displayed) with timeout=0

The primary factor affecting startup time appears to be that most resource/widgets are initialized upfront, and several widgets perform substantial work in their __init__ methods.

[sshane]

I'm pretty sure it's during some allocation in vipc connect. test_onroad is measuring uiDebug timings, which is after the UI starts

[adeebshihadeh]

Either move the blocking vipc recv into a thread like Qt (complex)

We have a blocking receive in the UI? We absolutely have to fix that. Nothing should be blocking in the main UI thread.