[09:21:28] <florent>	 kindrobot: No more luck with the selenium tests on Jenkins. I changed the default wait timeout from 5s to 30s to see
[14:17:23] <kindrobot>	 Thanks for the update florent. Zeljko thinks it likely that CI job can't reach the beta cluster.
[14:17:45] <kindrobot>	 There's a special job that can. It runs daily: https://m.mediawiki.org/wiki/Selenium/How-to/Run_tests_using_selenium-daily_Jenkins_job
[14:20:38] <kindrobot>	 So at least for now, we probably want to configure our CI not to run those selenium tests on merge, and instead run them as part of the daily job.
[14:21:16] <kindrobot>	 If you like, I can look at setting that up today, if you'd like to work on another e2e test.
[16:02:45] <zeljkof>	 Sorry florent and kindrobot, I didn't have much time today to work on this. I'll take a look next week. I'm not sure I understood the problem. There's a test that can only run on the beta cluster?
[16:05:06] <kindrobot>	 Yeah, the broader problem is that WikiLambda requires two services to run alongside the mediawiki (with wikilambda extension installed). My understanding after talking with releng is that there's not an easy way to do that in the current Jenkins setup.
[16:07:27] <kindrobot>	 This is why my top priority has been an ephemeral k8s test environment to run e2e tests against. But for now, running it against betacluster is a shortcut.