selenium:xvfb sometimes fails
-----------------------------
Key: MSELENIUM-25
URL: http://jira.codehaus.org/browse/MSELENIUM-25
Project: Maven 2.x Selenium Plugin
Issue Type: Bug
Components: xvfb
Affects Versions: 1.0-beta-2
Reporter: Jarek Gawor
Assignee: Jason Dillon
The selenium:xvfb sometimes fails with the following error:
INFO] [selenium:xvfb {execution: xvfb}]
[INFO] Starting Xvfb...
[INFO] Using display: :23
[INFO] Using Xauthority file: /tmp/Xvfb44522.Xauthority
[INFO] Deleting: /tmp/Xvfb44522.Xauthority
[WARNING] /usr/X11R6/bin/xauth: creating new authority file
/tmp/Xvfb44522.Xauthority
[WARNING] /usr/X11R6/bin/xauth: (argv):1: key contains odd number of
or non-hex characters
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] exec returned: 1
[INFO] ------------------------------------------------------------------------
[INFO] Trace
: exec returned: 1
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:636)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:662)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:487)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
I tracked it down to a problem in createCookie() method in XvfbMojo.groovy. The
toString(16) function drops leading zeros but apparently the xauth problem
always expects 32-byte hex value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
