Change Details

Pywikibot test are running on [[https://ci.appveyor.com/project/pywikibot-core/pywikibot/history | Appveyor]] for 9 years, exclusively for Windows OS. But there is one main disadvantage with it: it needs ~4 hours to test one patch (for only 7 variants. I propose to migrate from Appveyor to GitHub action which also supports windows. [[https://github.com/wikimedia/pywikibot/actions/runs/9612766913 | Doctests]] for example runs already on Windows (and Mac OS as well). Advantages for migrating -- - GitHub needs only ~30 minutes for all tests whereas Appveyor needs 3,5 - 4,5 hours because there is only 1 concurrent job available - GitHub actions can be tested easily by a repository clone - Codecov upload fails with Python 3.7.0 which cannot be solved (T363651) - Codecov upload fails with Python 3.11 (T365943 - Tests for Python 3.13 is available - Minor maintenance needed for only one test platform (beside jenkins CI) Disadvantages for migrating -- - gui_tests cannot be run on GitHub (T317618) - Appveyor provides 32 and 64 bit architecture, no glue whether this can be set up in GitHub. But does it really care? See [[https://github.com/python-pillow/Pillow/issues/7251 | Pillow issue 7251]] See also: T296371

Pywikibot test are running on [[https://ci.appveyor.com/project/pywikibot-core/pywikibot/history | Appveyor]] for 9 years, exclusively for Windows OS. But there is one main disadvantage with it: it needs ~4 hours to test one patch (for only 7 variants. I propose to migrate from Appveyor to GitHub action which also supports windows. [[https://github.com/wikimedia/pywikibot/actions/runs/9612766913 | Doctests]] for example runs already on Windows (and Mac OS as well). Advantages for migrating -- - GitHub needs only ~30 minutes for all tests whereas Appveyor needs 3,5 - 4,5 hours because there is only 1 concurrent job available - GitHub actions can be tested easily by a repository clone - Codecov upload fails with Python 3.7.0 which cannot be solved (T363651) - Codecov upload fails with Python 3.11 (T365943 - Tests for Python 3.13 is available - Minor maintenance needed for only one test platform (beside jenkins CI) - ... Disadvantages for migrating -- - gui_tests cannot be run on GitHub (T317618) - Appveyor provides 32 and 64 bit architecture, no glue whether this can be set up in GitHub. But does it really care? See [[https://github.com/python-pillow/Pillow/issues/7251 | Pillow issue 7251]] - ... See also: T296371

Pywikibot test are running on [[https://ci.appveyor.com/project/pywikibot-core/pywikibot/history | Appveyor]] for 9 years, exclusively for Windows OS. But there is one main disadvantage with it: it needs ~4 hours to test one patch (for only 7 variants. I propose to migrate from Appveyor to GitHub action which also supports windows. [[https://github.com/wikimedia/pywikibot/actions/runs/9612766913 | Doctests]] for example runs already on Windows (and Mac OS as well). Advantages for migrating -- - GitHub needs only ~30 minutes for all tests whereas Appveyor needs 3,5 - 4,5 hours because there is only 1 concurrent job available - GitHub actions can be tested easily by a repository clone - Codecov upload fails with Python 3.7.0 which cannot be solved (T363651) - Codecov upload fails with Python 3.11 (T365943 - Tests for Python 3.13 is available - Minor maintenance needed for only one test platform (beside jenkins CI) - ... Disadvantages for migrating -- - gui_tests cannot be run on GitHub (T317618) - Appveyor provides 32 and 64 bit architecture, no glue whether this can be set up in GitHub. But does it really care? See [[https://github.com/python-pillow/Pillow/issues/7251 | Pillow issue 7251]] - ... See also: T296371