Jon
Jon
I am also pairing Panther and ParaTest, and I am very happy with it so far. I have found this port algo to be extremely reliable: ``` ['port' => 9000...
(I have built a retry device for flaky browser tests, and I did have a situation where instances of ChromeDriver were not exiting, and thus a port conflict occurred. But...
@AntoineMUSSARD I don't have my work machine handy to remind me how I did this, but this looks wrong: ``` '--port=(int)(9515 + getmypid())' ``` This is just a string supplied...
@AntoineMUSSARD - I now have my code available. The base call is: ``` $client = Client::createChromeClient( $this->getTestDir() . '/scripts/chromedriver', // Or null if you want to auto-lookup $this->getChromeArguments(), $this->getDriverOptions() );...
I wonder if this bug should be logged against [Propel2](https://github.com/propelorm/Propel2) instead?
And a "yes please" from me too, I've just switched to `dev-master` to fix the migration diff issue.
What version of Propel are you using? Can we see the smallest possible script that replicates this problem?
What version of Propel are you running? Can we see the smallest possible replication script and a schema.xml?
This sounds like a support question, and so the bug tracker is probably not the best place for it. I'd suggest Reddit or Stack Overflow. In either case it is...
Is this a feature request? Propel1 is in security fix updates only, as far as I know. If you sure the question belongs here, it's worth showing what you are...