| WMDE-leszek added a comment. |
What @Krinkle has suggested sounds like a good plan at glance!
We just need to make sure that all tests are run in such set up. I will be looking at differences between jobs, and keep spamming here if I find something relevant.
Wikimedia solely uses MySQL, my understanding is that the sqlite jobs were kept around since developers tend to use sqlite on their development box.
This in general sounds like a good explanation of why sqlite jobs are around. As such it makes them quite good candidates for jobs to be kicked out.
However, as far as I understand, there are few tests that are skipped in mysql jobs and only run as part of sqlite jobs. Those are test of functionality where there some more complex DB queries are done. PHPUnit test use temporary tables and MySQL does not allow self-joins on temporary tables, so those test must be skipped. We still want to have those test run, so that seems like a good reason to
That said, there is only a handful of such tests. Maybe it makes sense to have a sqlite job running only those tests that are skipped in mysql jobs? That would should be quite performant, I assume. We could use a separate @group tag for those or so.
As far as I know, for such a sqlite job it would not be needed to have repo/client split (just run test with both components enabled), same for php55/hhvm (hhvm should be enough I guess).
Cc: WMDE-leszek, Krinkle, Paladox, Ladsgroup, greg, Tobi_WMDE_SW, daniel, Lydia_Pintscher, Addshore, thcipriani, hashar, Aklapper, QZanden, Salgo60, Izno, Wikidata-bugs, aude, Mbch331, Jay8g
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
