74502[BUGFIX] Detect arm64 and switch selenium docker image
Commit message
Review
-
Code review CR +2 Done
- Oli Bartsch +2
- Josef Glatz +1
- André Buchmann +1
-
Verified V +2 Done
- Oli Bartsch +2
- Josef Glatz +1
- core-ci +1 CI
Issues 1
Files 2
Review log 1315
-
Jochen Roth uploaded patch set 1 05/03/22, 09:33
-
core-ci voted on patch set 1 V +1 05/03/22, 09:41 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/26762
-
Oli Bartsch voted on patch set 1 V +1 CR +1 05/03/22, 09:52
-
Oli Bartsch updated the commit message in patch set 2 05/03/22, 09:52
-
Oli Bartsch voted on patch set 2 V +1 CR +1 05/03/22, 09:52
-
Josef Glatz commented on patch set 2 05/03/22, 09:55
-
core-ci voted on patch set 2 V +1 05/03/22, 10:01 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/26764
-
Jochen Roth commented on patch set 2 05/03/22, 10:07
runTests.sh:340ReplyThis are different docker images. So the tags are not in sync. `4.1.2-20220227` was the version that worked on M1. -
Josef Glatz commented on patch set 2 05/03/22, 10:35
runTests.sh:340Replyyeah. I know that they arw different images. but what about updating also the „official“ image to use selenium 4.1.x? i was just wondering if this reduces possible problems. i‘m not deep into selenium. -
Jochen Roth commented on patch set 2 05/03/22, 10:54
runTests.sh:340ReplyLast time i tried it did not work. I'll keep that in mind for later. -
Josef Glatz commented on patch set 2 05/03/22, 11:05
runTests.sh:340ReplyDone -
Josef Glatz voted on patch set 2 V +1 CR +1 05/04/22, 08:48
-
André Buchmann voted on patch set 2 CR +1 05/04/22, 09:09
-
Oli Bartsch voted on patch set 2 V +2 CR +2 05/04/22, 09:17
-
Oli Bartsch merged patch set 3 05/04/22, 09:17
runTests.sh:340