tests can fail if a display is in use

[totaam]

Issue migrated from trac ticket # 1965

component: packaging | priority: blocker | resolution: fixed

2018-09-20 05:57:59: antoine created the issue

---

If a vfb is left running from an aborted or failed test then we may try to start a new one on the same display number and fail.

Detected thanks to r20471. Somewhat related to #1963.

[totaam]

2018-09-20 05:59:21: antoine changed status from new to assigned

[totaam]

2018-09-20 05:59:21: antoine edited the issue description

[totaam]

2018-09-22 16:33:01: antoine changed status from assigned to closed

[totaam]

2018-09-22 16:33:01: antoine set resolution to fixed

[totaam]

2018-09-22 16:33:01: antoine commented

---

• r20472: don't fail if the socket is not removed, log a warning - may undo this one, sockets should always end up being removed!
• r20473: use a private xauth file that we cleanup afterwards, prevents relying on the file (not) existing and being in a good state (permissions, etc)
• r20475 bug fix for xauth paths

More test improvements: r20474, r20476, r20492, r20493, r20495

The tests now run without errors again, including on the new buildbot!

The new buildbot also uses nspawn to protect and better isolate the host from the build environment. So failures in one build "chroot" should not caused failures for other distros.