hashar added a comment.

At first: keep the job tied to the BrowserTests label. it is exactly meant for that. Specially the Wikibase job takes a while and would keep a Nodepool instance busy for a while. Maybe that is enough to fix it?

Then once it runs on BrowserTests, you would be able to reproduce and debug the failure directly on the slave. It is doable with a Nodepool instance but it is far less convenient :]


TASK DETAIL
https://phabricator.wikimedia.org/T167432

EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: zeljkofilipin, hashar
Cc: gerritbot, PokestarFan, Tobi_WMDE_SW, Jonas, thiemowmde, WMDE-leszek, zeljkofilipin, hashar, Aleksey_WMDE, Aklapper, Lordiis, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Lewizho99, Maathavan, Liudvikas, Izno, Luke081515, thcipriani, Wikidata-bugs, aude, Mbch331, Jay8g, greg
_______________________________________________
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to