-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Behat re-run fails on server not availalbe. #20
Comments
Discovered while testing #14 |
Wow, curious. Only 34_STABLE? And you did nothing to force the automatic rerun? Maybe we used to rerun automatically then? In any case, I think it's all the same script ( |
Ah, I see we are passing the Uhm... sure there is an explanation... |
I did not test with any other version. I think it is just
It defaults to 2 as you found already. Thanks for input re same script use BTW. May be I'll add some debugging output and see what happens. |
The issue is purely related to Moodle 3.4 used in test, that fails on behat test (using chrome profile) in the the latest Behat test forcing failure has been run using 3.9 stable to check re-run behaviour (in both Chrome and Firefox): Closing the issue. |
Here is an example: https://travis-ci.org/github/kabalin/moodle-plugin-ci/jobs/710005386#L2424
Not sure how re-run works, is it triggered as part of same command, or we somehow stop servers by the time it tries again. Need to investigate. It is easy to replicate with build of
moodle-plugin-ci
itself forMOODLE_34_STABLE
.The text was updated successfully, but these errors were encountered: