e2e: enable OPcache for the dev server instead of multi-process workers

The previous PHP_CLI_SERVER_WORKERS approach caused flaky e2e runs: PHP's
built-in server runs with OPcache disabled by default, so it recompiles the
whole TYPO3 codebase on every request, and each of the 8 worker processes
cold-started the framework on its first request. On CI the first attempt of
each test then ran ~20-60s and timed out while retries (hitting warmed
processes) passed — i.e. intermittent failures depending on which worker
served a request.

Run a single built-in-server process with OPcache enabled instead. After the
codebase is compiled on the first request(s) the process serves subsequent
requests quickly and deterministically, so a single warmed process is more
reliable here than several cold-starting workers. Timeouts are bumped to give
that first compile headroom on slower runners.

Validated locally on PHP 8.4 for TYPO3 12.4 and 14.3: 4 passed each, no flaky
retries.

https://claude.ai/code/session_01DaMNs9bAk3ofegnToxwF7X

Author: claude

Build/playwright.config.ts

@@ -3,8 +3,10 @@ import config from './tests/playwright/config';
 
 export default defineConfig({
   testDir: './tests/playwright',
-  timeout: 60000,
-  expect: { timeout: 15000 },
+  // Generous timeouts: the first requests served by the PHP built-in server
+  // compile the TYPO3 codebase into OPcache, which is slow on CI runners.
+  timeout: 90000,
+  expect: { timeout: 25000 },
   fullyParallel: false,
   forbidOnly: !!process.env.CI,
   retries: process.env.CI ? 2 : 0,

Build/runTests.sh

@@ -242,13 +242,19 @@ LOCAL_WEB_URL="http://${LOCAL_WEB_HOST}:${LOCAL_WEB_PORT}"
 
 echo "Starting PHP built-in web server at ${LOCAL_WEB_URL}..."
 mkdir -p var/log
-# The TYPO3 backend loads many JavaScript (ES module) and asset requests in
-# parallel. The PHP built-in web server is single-threaded by default, which
-# serializes those requests and, on slower (CI) machines, makes the backend
-# module content miss the test timeout. Spawn multiple worker processes so the
-# server can answer requests concurrently.
-PHP_CLI_SERVER_WORKERS="${PHP_CLI_SERVER_WORKERS:-8}" \
-    php -S "${LOCAL_WEB_HOST}:${LOCAL_WEB_PORT}" -t public/ >"${ROOT_DIR}/var/log/typo3-e2e-web.log" 2>&1 &
+# The PHP built-in web server is single-threaded and runs with OPcache disabled
+# by default, so it otherwise recompiles the whole TYPO3 codebase on every
+# request. On slower (CI) machines that makes the backend module content miss
+# the test timeout. Enabling OPcache lets the single process serve requests
+# quickly once the codebase is compiled on the first request(s). A single
+# (warmed) process is also more reliable here than multiple worker processes,
+# which would each cold-start the framework on their first request.
+php \
+    -d opcache.enable_cli=1 \
+    -d opcache.memory_consumption=256 \
+    -d opcache.max_accelerated_files=30000 \
+    -d opcache.validate_timestamps=0 \
+    -S "${LOCAL_WEB_HOST}:${LOCAL_WEB_PORT}" -t public/ >"${ROOT_DIR}/var/log/typo3-e2e-web.log" 2>&1 &
 LOCAL_WEB_PID=$!
 
 echo "Waiting for TYPO3..."