| Peter | |
| Feb 25 2026, 3:45 PM |
| F72416235: Screenshot 2026-02-25 at 16.41.13.png | |
| Feb 25 2026, 3:45 PM |
We have a test that been the most flakey one when we started to run tests in parallel:
Looking at the tests, I think it could be an issue if other tests also change content (and we check that our change is first in the array). Lets change this one so we do not look for having our change first in the list, instead look that we actually have the change in the change list.
Change #1246902 had a related patch set uploaded (by Phedenskog; author: Phedenskog):
[mediawiki/core@master] selenium: Use rctitle to only look for our change
Change #1246903 had a related patch set uploaded (by Phedenskog; author: Phedenskog):
[mediawiki/core@master] selenium: Cleanup wait logic for recent changes
Change #1246902 abandoned by Phedenskog:
[mediawiki/core@master] selenium: Use rctitle to only check for our change
Reason:
The tests is still flakey
Change #1247052 had a related patch set uploaded (by Phedenskog; author: Phedenskog):
[mediawiki/core@master] selenium: Cleanup wait logic for recent changes
Change #1246903 abandoned by Phedenskog:
[mediawiki/core@master] selenium: Cleanup wait logic for recent changes
Reason:
Doing another cleanup
Change #1247024 had a related patch set uploaded (by Phedenskog; author: Phedenskog):
[mediawiki/core@master] selenium: Make sure our change is in the list (not first)
Change #1247024 merged by jenkins-bot:
[mediawiki/core@master] selenium: Make sure our change is in the list (not first)
Change #1247052 merged by jenkins-bot:
[mediawiki/core@master] selenium: Cleanup wait logic for recent changes