-
Bug
-
Resolution: Won't Fix
-
Minor
-
None
-
3.8.3, 3.9
-
None
-
MOODLE_38_STABLE, MOODLE_39_STABLE
This is a followup / related to MDL-66263 where the discussion was raised by timhunt.
Historically, we have followed a lowest & highest strategy about deciding which php versions were used for testing in travis.
In the linked issue, for Moodle 3.9 - for example, it was commented:
I don't acutally understand the logic of doing 3 PHPunit runs, two on PHP 7.4 and one on PHP 7.2. Surely it would be better to do one each on 7.2, 7.3 and 7.4 (I agree with doing 2 on postgres and 1 on MySQL).
Also, if it is worth running the fast things on multiple versions of PHP, then we should run them on all supported PHP versions. (Or, we should only run them on one PHP version). But, they are so fast that I don't see a good reason for doing 2/3.
Anyway, that is what I think. If you don't like my opinion, you are welcome to find another Peer reviewer :-p (But, before you do, you might like to update the comment that says "We only run MySQL on PHP 7.2, so run that first.")
So this is about to prospect if we can use some alternative (and better) strategy / matrix of jobs than the current one.
Ciao
- Discovered while testing
-
MDL-66263 Bump Travis max version to 7.4
-
- Closed
-
- has a non-specific relationship to
-
MDLSITE-7135 Remove Travis integration from Moodle core
-
- Closed
-