-
Notifications
You must be signed in to change notification settings - Fork 262
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 failing on moodle 4.0 / current master #207
Comments
Uhm, @PhMemmel , have you you got it working? Sorry for the late reply but I cannot find anything causing that problem and both CI and local runs say this is working with 400 and 4.1dev (master) perfectly. If there is any other detail able to make us reproduce the problem, great, but right now it seems that everything is working ok, so far. Ciao :-) |
Hi @stronk7, thank you picking up on this. I managed to get it back to work and simply forgot to close this issue, sorry for that. Unfortunately, too much time has passed since then so I do not really remember how I fixed it, but it was nothing related to the docker repo. Again thx and sry, Issue closed. |
Thanks! |
I saw this on current |
Hi @mackensen, Shortly a recent change in the PHP base image requires the user to be specified when creating soft links in the container: HTH, |
Also, note that Moodle still doesn't support php82, it's WIP @ https://tracker.moodle.org/browse/MDL-76405 |
I've tried to run behat test with a clean moodle repository with master branch
I set
MOODLE_DOCKER_WWWROOT
to the moodle repo andMOODLE_DOCKER_DB
tomariadb
.Running behatinit is working perfectly. However, running
bin/moodle-docker-compose exec -u www-data webserver php admin/tool/behat/cli/run.php --tags=@block_search_forums
(just an example tag) leads to:This seems to be related to moodle 4.0. Switching to
MOODLE_311_STABLE
, rerunning behat init and executing the command above everything works without a problem.The text was updated successfully, but these errors were encountered: