37321187009
100%

Ran 05 Oct 2026 02:03PM UTC

Jobs 1

Files 6

Run time 1min

Badge

Embed ▾

Committed 05 Oct 2026 02:00PM UTC coverage: 100.0%. Remained the same

Build # 37321187009

Build Type

push

github

Committed by

web-flow

Commit Message

[TASK] Align `cleanUp()` with the TYPO3 Core `runTests.sh` (#2365)

Use `kill` and remove the network with `-f` only on Podman, Like the
Core does. This reverts the `rm -f` workaround from #2324.

The errors in #2125 came from the AppArmor profiles on Ubuntu 24.04
denying crun to signal containers (LP#2040483, fixed in podman
4.9.3+ds1-1ubuntu0.2), and from `network rm` without `-f` on podman.
With `kill`, cleanup cycles per database on docker 29.8.2 and
on podman 4.9.3/crun (rootless, Ubuntu 24.04) showed no errors and no
leftover containers or networks.

`rm -f` also slows down the cleanup on Podman: it sends SIGTERM and
waits 10 seconds before SIGKILL, and MariaDB and MySQL do not stop
within that time. Every `rm -f` cycle with MariaDB or
MySQL printed a "StopSignal SIGTERM failed" warning.

Fixes #2201

Coverage Stats

126 of 126 relevant lines covered (100.0%)

5.71 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	37321187009.1	05 Oct 2026 02:03PM UTC	6	100.0	GitHub Action Run

TYPO3BestPractices / tea / 37321187009
100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 37321187009

TYPO3BestPractices / tea / 37321187009 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 37321187009

TYPO3BestPractices / tea / 37321187009
100%

README BADGES
x