There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Please resubmit the form.
|Open||None||T270771 Keep selenium-daily-beta(commons)-MediaWiki Jenkins jobs green|
|Resolved||Eevans||T243123 Login to at least en.wikipedia.beta.wmflabs.org and commons.wikimedia.beta.wmflabs.org sometimes fails with `There seems to be a problem with your login session`|
- Mentioned In
- T263617: Cannot login to beta cluster: "There seems to be a problem with your login session..."
T249450: Getting Login Session Error when running tests with Cypress
T250986: Login to some beta wikis fail with "There seems to be a problem with your login session"
T243669: Travis fails on generate_family_file_tests.TestGenerateFamilyFiles
T224712: Attempt to login fails several times
T245125: Login to en.wikisource.beta.wmflabs.org always fails with session error
rMSKS662f71ebf9bc: Configurable query and connect timeouts
T243266: Fix failing TwoColConflict selenium-daily
- Mentioned Here
- T224712: Attempt to login fails several times
+1 selenium-daily-beta-TwoColConflict seems to fail due to that also since 2020-01-20. ( at least I get the errors when I try to reproduce the issue targeting the beta cluster )
It looks like Cassandra queries from Kask have been intermittently timing out. Both Kask and Cassandra are co-located on the same VM, and it is pretty resource constrained, but AFAIK it has been working OK to this point; We can probably begin with a restart and go from there
In the meantime, I'm going to use this as an opportunity to see if Kask can be made more resilient to these sorts of timeouts, and/or better report on them.
It seems to be working OK at the moment so I'm going to downgrade the priority. Feel free to bump it back up if something changes.
Sooo this issue is still responsible for the Two-Column-Edit-Conflict-Merge daily selenium test failing every day for some time (125). The build artifacts are not very helpful, but when I run the tests from my local machine facing beta I still get a couple of login errors and lost sessions at random points during the test run. - Is anyone working on this or feels responsible at least?
Looking at the tests linked by @zeljkofilipin that do not fail every day, I could add that the Two-Column-Edit-Conflict-Merge tests create an additional account in the background that uses the MWBot to login and edit a page. The tests also need to login once for every spec to enable the beta feature of the extension.
@Eevans I don't know much about MediaWiki-Vagrant internals. I've been useing MediaWiki-Vagrant for years and I don't think I've ever seen that error. I've assumed it's the same problem, because the error message was the same. If nobody else has that problem, maybe it's something specific to my machine.
I don't remember which roles I had enabled at the time, sorry. I've either had no roles, or minerva, or templatewizard, because that's what I've been working on yesterday. The error happened only once.