[Webkit-unassigned] [Bug 88414] [NRWT] the XvfbDriver should chose the next free display

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jun 7 02:49:20 PDT 2012


--- Comment #3 from Csaba Osztrogonac <ossy at webkit.org>  2012-06-07 02:49:19 PST ---
(From update of attachment 146020)
View in context: https://bugs.webkit.org/attachment.cgi?id=146020&action=review

> Tools/Scripts/webkitpy/layout_tests/port/xvfbdriver.py:54
> +        def next_free_id():
> +            for i in range(99):
> +                if not os.path.exists('/tmp/.X%d-lock' % i):
> +                    return i

Hmm ... I think checking /tmp/.X%d-lock isn't enough ...
On the machine where run 3 buildslave, I have only
these lock files: .X0-lock, .X90-lock .
But there are three xvfb-run.XXXXXX directories
with Xauthority files contain the following numbers: 84, 39, 90.
(These numbers were passed to xvfb-run when we started the bots.)
And there are two sockets in /tmp/.X11-unix dir: X0 and X90.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list