|
|
|
[
Permlink
| « Hide
]
Andras Hatvani - 27/Aug/08 01:04 PM
As a workaround you can use a pre-configured profile, so this no blocker and thus I'd suggest to reduce priority.
That means adding a profile to each build slave we're running. This is a bit too much work?
Is there a problem with adding the said patch? Does it need more testing? (I can assist with that) Ok. I misunderstood. You meant following this: http://clearspace.openqa.org/thread/14617
That worked, but I had to rewrite the SeleniumAntTask to support an arbitrary browser string in order to pass in the right arguments. (I'm using 1.0 beta) FWIW, I agree that the priority should be lowered. It's not critical.
Cannot reproduce - if still present though, then please provide a reproducible test scenario.
I've switched jobs since my previous comments, so I can't reproduce this now.
But for reference, this happened when running a test suite using the Ant-task and Firefox. I can't remember if it happened only when running under a user that had not started firefox, such as the buildbot account on our test servers. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||