- 09 May, 2022 1 commit
-
-
Christian Kuhn authored
We restricted the default retry of single jobs a while ago to do that only for acceptance test related jobs. This does not work out well: There are simply to many things that occassionally false-negative due to network, timing or other issues. The patch adds general retry:1 for all jobs for mental sanity. Resolves: #97597 Related: #96999 Releases: main, 11.5 Change-Id: I408b7ef1b6c6145dc1b5b12bc4550c00dfdaa930 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74584 Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
core-ci <typo3@b13.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
- 22 Feb, 2022 1 commit
-
-
Acceptance tests are the most likely tests to recover properly when automaticly retrying on test execution failure. CGL, integration, unit and functional tests on the other hand are more likely to fail with real issues and retry won't fix these issues, thus wasting CI execution time and job slots. The patch changes the default retry back to zero retries, except for 'acceptance' tests, including 'acceptanceInstall' tests. Resolves: #96999 Releases: main, 11.5 Change-Id: I570c7fc6c61fe55ab5f60b51c04161f935876d24 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73647 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 24 Jan, 2022 1 commit
-
-
Gitlab is able to give a nice overview of tests and how often a test failed recently which makes it easier to investigate flaky/failed tests. Also it takes away the pain of searching for the actual failing test in a job because it only displays information of the failed test (no bootstrap log details and such) Codeception AC test reports have been added to the Gitlab GUI using the --xml flag to generate a Gitlab readable report format and it has been added to the jobs artifacts:reports:junit. Resolves: #96628 Releases: main, 11.5 Change-Id: Id5ab5adfdc318c0c97143b0f05311f47fd1d37f0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73136 Tested-by:
core-ci <typo3@b13.com>
Tested-by: 
Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 18 Jan, 2022 1 commit
-
-
System Requirements have been announced for TYPO3 v12 [1]: PHP 8.1 and higher, raised minimum DBMS versions and removed mssql support. The patch sets according PHP requirements in the central composer.json files: > composer config platform.php 8.1.1 > composer req php:"^8.1" > composer req php:"^8.1" -d typo3/sysext/core --no-update The patch adjusts the core main test suite to run tests with PHP 8.1, ignoring older PHP releases, drops mssql from the test suites and raises versions of other DBMS in the test suite. The option set of Build/Scripts/runTests.sh is updated accordingly. phpstan needs a special handling since it is not PHP 8.1 ready, yet: The code scanner is still run using PHP 8.0 for now. With the default charset being changed to utf8 in mysql, an acceptance tests becomes obsolete and is substituted with an @todo comment to further investigate if we could streamline the underlying code in the install tool. [1] https://typo3.org/article/new-system-requirements-for-upcoming-typo3-v12 Resolves: #96553 Releases: main Change-Id: I34981523dffe6c650a1126c0002f3fa519e11c65 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73035 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Benni Mack <benni@typo3.org> Reviewed-by:
-
- 29 Nov, 2021 1 commit
-
-
Christian Kuhn authored
Change-Id: I13ca3c60a040c15aca8e259e7c65d33682f37c44 Resolves: #96131 Releases: main Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72349 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 15 Nov, 2021 1 commit
-
-
The big win with this patch: All core now run tests with E_ALL error handling (unit, functional, acceptance). This means, they will also fail when PHP deprecations are raised. This improves PHP compatibility and makes sure new PHP versions can be integrated more quickly since we'll find deprecated PHP code calls early. Additionally, the acceptance tests are extended to run with PHP 8.1. As a result, the entire testing is now done with PHP 8.1 and green, we can claim PHP 8.1 compatibility for core now. Resolves: #95981 Releases: master Change-Id: I1eece6d2faec6453ada9731fc4064076dc8d5d97 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72151 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Jochen <rothjochen@gmail.com>
Tested-by: Jochen <rothjochen@gmail.com>
Reviewed-by:
-
- 13 Aug, 2021 1 commit
-
-
Andreas Fernandez authored
To be more consistent: * Rename "-s install" to "-s acceptanceInstall" * Rename "-s cglAll" to "-s cgl" * Rename "-s lint" to "-s lintPhp" Apart from that, the cgl checker also lints the files before checking cgl. The explicit pre-merge lint jobs are thus obsolete in pre-merge. We keep "lint everything" for nightlies to be sure. Resolves: #94769 Releases: master Change-Id: Ie7b409f3b2485a8792199e4ad2eaec8565daf253 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70340 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
-
- 14 Jun, 2021 1 commit
-
-
Christian Kuhn authored
After a long way of fixing our code base to have all our tests (unit, functional, acceptance tests) green, TYPO3 now officially runs with PHP 8.0. TYPO3 v11 LTS thus will support PHP 7.4 and PHP 8.0 (and hopefully PHP 8.1 once the dependencies support PHP 8.1). There might be a few PHP notices throughout TYPO3 Frontend and Backend, but all base functionality is now available for PHP 8.0 as well. Resolves: #93631 Related: #94057 Releases: master Change-Id: I5798e6f49ee637b794df096fd44b8157d96b74bc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69489 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 28 Feb, 2021 1 commit
-
-
Each jobs will have one more run in case it fails in the first. This will prevent pipeline failures due to recoverable test run failures. Resolves: #93603 Releases: master, 10.4, 9.5 Change-Id: Ia054973d1f2a336727ef9d483041f1f48147c375 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68140 Tested-by:
Simon Gilli <typo3@gilbertsoft.org>
Tested-by: TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com>
Tested-by: Simon Gilli <typo3@gilbertsoft.org>
Reviewed-by:
-
- 05 Feb, 2021 1 commit
-
-
When a patch is pushed to gerrit, the gerrit-adapter middleware also synchronizes the master branch. This triggers two pipelines if patches have been merged meanwhile. Suppress the master pipeline run: All patches should have been tested already and a run for current master is done with the nightly tasks anyway. Change-Id: I78e9070588027d5fa10f11e63ab3e2677a225094 Resolves: #93438 Releases: master Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67646 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 03 Feb, 2021 1 commit
-
-
Christian Kuhn authored
A first Build/gitlab-ci.yml for master. Core v10 and v9 will have dedicated patches. This specifies jobs executed via gitlab CI for master pre-merge "a patch has been pushed" and nightly builds. This uses a new testing infrastructure defined by https://gitlab.typo3.org/core-testing/testing-infrastructure to execute test suites. Resolves: #93406 Releases: master Change-Id: I377ac59478925b789f63871c8fa6c3b2d5b2a839 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67626 Tested-by:
Simon Gilli <typo3@gilbertsoft.org>
Tested-by: Simon Gilli <typo3@gilbertsoft.org>
Reviewed-by:
-
