Bug 242327 – GTK-WK2-Tests-EWS: Unexpected infrastructure issue: RuntimeError: Unable to start Xvfb display server

• Status: RESOLVED
• Resolution: FIXED
• Component: WebKitGTK

[Fujii Hironori]

GTK-WK2-Tests-EWS is reporting an error randomly now.

https://ews-build.webkit.org/#/builders/35

> Unexpected infrastructure issue: The layout-test run with change generated no list of results and exited with error, retrying with the hope it was a random infrastructure error. Retrying build [retry count is 0 of 3]

> RuntimeError: Unable to start Xvfb display server (from worker/14)

[Fujii Hironori]

This is annoying. You can check how often this issue is happening now by searching "Unexpected infrastructure issue" in the page https://ews-build.webkit.org/#/builders/35

[Carlos Alberto Lopez Perez]

This is more or less expected.

There are race conditions when starting the WPT servers or the Xvfb server that sometimes prevent the test from working as expected.

The error that it raises "infrastructure error" is designed to detect that and retry the build in the hope that the next time it will work.

When this happens if you go to the page of the build you can see the retry on the last step (usually step 22), where it says: "trigger 0 builds, 1 pending builds" or similar. If you click on the arrow there to see what is inside the step you see how it schedules a new try, up to 3 times more.

For example, in https://ews-build.webkit.org/#/builders/35/builds/21901 if I go to step 22 and i click on it i go to https://ews-build.webkit.org/#/builders/36/builds/76503 which is the retry of the previous one and this one passed.


What are you finding annoying about this? AFAIK it should not send an e-mail to the developer when it retries a build due to infrastructure error.
Also the bubble should not be red, but orange in that case. That was at least the case with bugzilla. Is it showing a red bubble on github?

[Fujii Hironori]

I just saw an orange bubble on bugzilla. I checked it again, it is green now. Good to know. Thank you for the explanation.