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

Build: #67 was successful Rebuilt by Bamboo CLI Admin

Stages & jobs

  1. Preparation

  2. Integrity

  3. Unit Tests PHP72

  4. Unit Tests PHP73

  5. Unit Tests PHP74

  6. Acceptance mysql

  7. Functionals mssql PHP 7.3

  8. Acceptance sqlite

  9. Acceptance pgsql

  10. Functionals mssql PHP7.4

  11. Functionals mysql PHP 7.2

  12. Functionals mysql PHP 7.3

  13. Functionals mysql PHP 7.4

  14. Functionals pgsql

  15. Functionals sqlite

  16. Functionals mssql PHP 7.2

Build result summary


201 minutes
514079968f6c691e54bf5bc61f9c1a6db1410e98 514079968f6c691e54bf5bc61f9c1a6db1410e98
Total tests
Successful since
#58 ()
Number of retries


Code commits

Author Commit Message Commit date
Andreas Fernandez <a.fernandez@scripting-base.de> Andreas Fernandez <a.fernandez@scripting-base.de> 514079968f6c691e54bf5bc61f9c1a6db1410e98 514079968f6c691e54bf5bc61f9c1a6db1410e98 [BUGFIX] Do not generate site configuration for localized root pages
A new condition is added to the `CreateSiteConfiguration` DataHandler
hook which avoids the creation of a new site configuration for
localizations of root pages.

Resolves: #91845
Releases: master, 10.4
Change-Id: Ic51ba62600f4304920b66afe53b66e598404a104
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65107
Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
Reviewed-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
Christian Kuhn <lolli@schwarzbu.ch> Christian Kuhn <lolli@schwarzbu.ch> 51a9d0cc057d774e3be36342e7761496a0dfc0f3 51a9d0cc057d774e3be36342e7761496a0dfc0f3 [BUGFIX] No bogus log entries when discarding workspace records
Selecting a page and records on the page to be discarded in the
workspace module can lead to log entries that records could not
be deleted.
This can happen when discarding (deleting) a page that only exists
in the workspace already has deleted records on the page. The explicit
call to delete single records then creates this log.
The solution is to ask the DataHandler if the record in question
has already been deleted to avoid deletion in this case.
Additionally, the log entry now contains the table:uid to
make it more useful in case it pops up again.

Resolves: #61719
Releases: master, 10.4
Change-Id: I8fee34fad2484e9e656bcb5ff611a91374127d94
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65106
Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Daniel Goerz <daniel.goerz@posteo.de>
Reviewed-by: Daniel Goerz <daniel.goerz@posteo.de>