https://en.wikipedia.org/wiki/User:Pywikibot-test is logging in on lots of non-test Wikipedias, from many different locations, which clutters the login attempts dashboard used for monitoring login anomalies.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Xqt | T416357 Wikimedia Hackathon Northwestern Europe 2026 (PWB) | |||
| Resolved | Xqt | T419127 Pywikibot-test is active on non-test Wikipedias | |||
| Resolved | Xqt | T419203 Move ubuntu doctests for pypy 3.9 and Python 3.10-3.12 to Jenkins CI | |||
| Resolved | Xqt | T426484 Add proxy support to GitHub actions |
Thank you for pointing this out. Our tests run on Jenkins for CI and on GitHub for final tests in different environments. The later may cause issues, and a self-hosted runner could help, but I am unable to set on up. See T399485 for more details.
Some tests are intentionally run on life wikis which because there they coverL10N and i18n scenarios. However, we could reduce the default tests on enwiki and zhwikisource if this would help.
Yes, in principle, if it is reachable via URL. A corresponding Family can either acccessed via AutoFamily or by creating a family using generate_family_file script (or a family file has to be made by hand like those).
Tests that run in CI have already been removed from GitHib Action matrix. For your reference, the CI tests can be found here and the GitHub action workflow are listed in this folder.
I think this issue is resolved by T426484. Most post-CI tests are now run through the WMCS SOCKS proxy.