Execute TYPO3 core master pre-merge tests. Auto generated! See Build/bamboo of core git repository.

Build: #61 was successful Manual run by Bamboo CLI Admin

Build result summary


12 minutes
Custom build
9a3f936b87cef999de5d69a1090463b911d5ca9b 9a3f936b87cef999de5d69a1090463b911d5ca9b
Total tests
Successful since
#53 ()


Custom variables

Name Value
patchset 1
changeUrl 63238

Code commits

Author Commit Message Commit date
Benni Mack <benni@typo3.org> Benni Mack <benni@typo3.org> 9a3f936b87cef999de5d69a1090463b911d5ca9b 9a3f936b87cef999de5d69a1090463b911d5ca9b [BUGFIX] Run tests with configured error reporting in PHPunit
SystemEnvironmentBuilder calls

 error_reporting(E_ALL & ~(E_STRICT | E_NOTICE | E_DEPRECATED));

which in turn is called on every test to setup the environment.
This basically enforces this exact error reporting and does not
allow to configure the error reporting in phpunit.xml AT ALL.

Until TYPO3 v9, this was covered in each BaseTestCase in
setUpBeforeClass() to re-add E_NOTICE to make all tests run
without notice.

The functionality in SystemEnvironmentBuilder was added
in TYPO3 v6.0 while refactoring TYPO3's Bootstrap to ensure
that no notices in ext_localconf.php or ext_tables.php
were breaking the output. However, nowadays, TYPO3's
error reporting is set up directly after LocalConfiguration.php
inclusion, making this logic obsolete.

The functionality is therefore moved to the Bootstrap at a later point,
which is called for Functional and Acceptance Tests.

Resolves: #90125
Releases: master
Change-Id: I8d6348ffbf6622c03abecedc1cb0ce286ba1044c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62926
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>
Reviewed-by: Oliver Klee <typo3-coding@oliverklee.de>
Reviewed-by: Benni Mack <benni@typo3.org>
Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
Tested-by: Benni Mack <benni@typo3.org>

Jira issues

Unknown Issue TypeCHANGE-63238Could not obtain issue details from Jira
Unknown Issue TypePATCHSET-1Could not obtain issue details from Jira