[15:51:07] I am working on adding selenium tests for https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ProofreadPage/+/813328 (a feature for ProofreadPage that requires a two config variable to be set to work)... Is there any way to ensure this for selenium tests ? [15:52:00] *ensure that the config variables are set for selenium tests ? [16:11:38] I would presume so [16:11:42] No idea where to look/start though [16:53:20] Is the coverage queue broken? [16:53:47] https://integration.wikimedia.org/zuul/ says that there are changes waiting 30 mins for a coverage [16:54:54] Plus patches to the CheckUser extension always from my experience have the code coverage report done within a few mins and always before the tests are done. [16:55:14] While this time it's been waiting 17 mins with 0 mins to go till completion while the tests have completed [16:56:31] unlikely. IIRC the coverage queue is just set to a low priority, so when there is a lot to do for zuul, it will priorise the normal test queue and the gate-and-submit queue and other stuff like coverage or patch-performance has to wait. [16:58:25] Okay. Just concerned as I've not seen code coverage take that long [16:58:33] But that makes sense [17:03:15] (but I need to agree that the number of patches currently queued is quite low, so there might still be something broken here) [17:04:58] In -operations I was told that there are lots of idle executors [18:54:41] Dreamy_Jazz: It sometimes takes as long as ~6 hours, especially if the Wikidata team push a big stack of changes. But good to ask! [21:45:11] Does anyone know of an example of a test that replaces HttpRequestFactory with a mock? /me is being lazy and wants to copy-n-paste [21:48:17] Wikibase does [21:48:42] And Mathoid [21:48:55] * bd808 will check these out