-
Notifications
You must be signed in to change notification settings - Fork 17
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
Modernise CI #105
base: master
Are you sure you want to change the base?
Modernise CI #105
Conversation
* Adds CI for MW 1.43 * Uses gesinn-it-pub/docker-compose-ci for CI * Runs linting, phpcs and more * Fixes some phpcs errors - although not all. Fixes #103
@gesinn-it-gea / @gesinn-it-ilm requires gesinn-it-pub/docker-compose-ci#9 to be merged. |
Hmm even with that it is still throwing "Fatal error: Uncaught ExtensionDependencyError: SemanticScribunto requires Scribunto to be installed." |
Oh I missed a few places in gesinn-it-pub/docker-compose-ci#9. Although I think it has to be published for things to take affect? idk. |
Have no idea how to fix:
|
@gesinn-it-ilm @gesinn-it-gea not sure how to resolve ^? Unless it doesn't work on my Mac in docker. (I have a M1 Mac). The error in GitHub ci is because the gesinn-it-pub/docker-compose-ci#9 needs merging. For some reason it doesn't use the current build checkout. |
is still happening. I dunno if there's suppose to be a deployment of that change (CI?) |
For another repo I implemented a workflow to schedule automatic updates of docker-compose-ci: https://github.com/gesinn-it-pub/IDProvider/blob/master/.github/workflows/update-submodules.yml If you like this approach, you can add it to other repos as well. Instead of running this only on one day, we can run it daily |
I'm not using SemanticScribuntu. Maybe the way it is installed by docker-compose-ci needs to be changed (e.g. using composer to get the deps). Or make the deps being installable via docker-compose-ci |
I’m not sure. It works locally hence the error about lua returning that status number. |
I see that REL1_39 isn’t being supplied to where it fetches Scribunto which would be a problem. |
For some reason phpunit is now in an infinite loop. I don't know why. |
@gesinn-it-ilm dunno how we fix:
Seems related to your change switching to MW integration class. Also dunno how we fix:
|
@gesinn-it-gea / @gesinn-it-ilm looks like https://github.com/wikimedia/mediawiki/blob/17e259ef2475f56635cf3c4651c81606f8be62bb/tests/phpunit/includes/TestUser.php#L35 So wgDBprefix isn't unittest_. I don't know how to fix that. Looks like SMW needs its test fixing which is out of my experience (I would have no clue how to do it). There's https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/tests/phpunit/Utils/Connection/TestDatabaseTableBuilder.php#L71 and https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/tests/phpunit/Utils/Connection/TestDatabaseTableBuilder.php#L237 |
Looks like we re-added it under the new name cc @gesinn-it-gea / @gesinn-it-ilm . I guess things need to be fixed to conform to MW Integration test class? |
Maybe the whole JSONScript runner need to be updated. Compare with other places where we use it, e.g. https://github.com/SemanticMediaWiki/SemanticDrilldown/blob/master/tests/phpunit/Integration/JSONScript/JsonTestCaseScriptRunnerTest.php or https://github.com/SemanticMediaWiki/SemanticResultFormats/tree/master/tests/phpunit/Integration/JSONScript |
@gesinn-it-gea do you mean changing to JSONScriptTestCaseRunnerTest? Not too sure that will help much here. We can try it. |
Doesn't fix the problem. MW 1.39 it's just a infinite recursion and in mw 1.42 it at least show the errors (the same one). |
Fixes #103