#96079Allow tests to be run with stable docker-compose v2 installed - for working versions
Description
It looks like there are stable versions of docker-compose v2 that prevent the tests from being run by the check introduced in #95057 (https://github.com/typo3/typo3/commit/3c00759dd6070c392f4c2b72189d2057543e9ba0)
At least my tests with Docker Compose v2.1.1 did work fine under Linux, after commenting out the check in runTests.sh.
The check should be refined to allow users of a stable (working) v2 version to run the tests.
Reviews 1
History 217
-
Gerrit Code Review pushed patch set 1 for main to change 74191 status
NewUnder Review 04/05/22, 20:14 -
Gerrit Code Review pushed patch set 2 for main to change 74191 04/05/22, 20:19
-
Gerrit Code Review pushed patch set 3 for main to change 74191 04/05/22, 20:32
-
Gerrit Code Review pushed patch set 4 for main to change 74191 04/05/22, 20:41
-
Gerrit Code Review pushed patch set 5 for main to change 74191 04/05/22, 22:17
-
Gerrit Code Review pushed patch set 6 for main to change 74191 04/06/22, 07:22
-
Gerrit Code Review pushed patch set 7 for main to change 74191 04/06/22, 08:32
-
Gerrit Code Review pushed patch set 8 for main to change 74191 04/06/22, 08:41
-
Gerrit Code Review pushed patch set 9 for main to change 74191 04/06/22, 10:06
-
Gerrit Code Review pushed patch set 10 for main to change 74191 04/06/22, 10:26
-
Gerrit Code Review pushed patch set 11 for main to change 74191 04/06/22, 11:13
-
Gerrit Code Review pushed patch set 12 for main to change 74191 04/06/22, 14:43
-
Gerrit Code Review pushed patch set 13 for main to change 74191 04/06/22, 14:44
-
Gerrit Code Review pushed patch set 14 for main to change 74191 04/06/22, 14:46
-
Gerrit Code Review pushed patch set 15 for main to change 74191 04/06/22, 15:12
-
Simon Schaufelberger commented and changed status
Under ReviewNew 07/03/23, 01:49 -
Michael Telgkamp commented and changed status
NewClosed 06/11/24, 17:05Docker compose is not used in runTests any longer. This ticket is not relevant any longer.
The referenced patch has nothing to do with this issue.