fix(ci): throttle Playwright shards and surface keycloak boot logs on failure - #2542
Open
shikanime wants to merge 3 commits into
Open
fix(ci): throttle Playwright shards and surface keycloak boot logs on failure#2542shikanime wants to merge 3 commits into
shikanime wants to merge 3 commits into
Conversation
shikanime
force-pushed
the
fix/playwright-keycloak-flake
branch
from
August 21, 2026 08:54
e351539 to
613d7da
Compare
shikanime
marked this pull request as ready for review
August 21, 2026 08:57
iliesmrf
previously approved these changes
Aug 21, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 21, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 21, 2026
shikanime
force-pushed
the
fix/playwright-keycloak-flake
branch
from
August 21, 2026 12:29
613d7da to
b6dbabf
Compare
Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr> Change-Id: Ifdc20eb6771981647bd97bb1c33028c06a6a6964
shikanime
force-pushed
the
fix/playwright-keycloak-flake
branch
from
August 21, 2026 12:30
b6dbabf to
e7a2e37
Compare
shikanime
enabled auto-merge
August 21, 2026 12:31
2 tasks
This was referenced Aug 21, 2026
shikanime
force-pushed
the
fix/playwright-keycloak-flake
branch
from
August 21, 2026 13:11
31c9218 to
205f6c7
Compare
Co-authored-by: Automata <automata@shikanime.studio>
shikanime
force-pushed
the
fix/playwright-keycloak-flake
branch
from
August 21, 2026 13:31
205f6c7 to
1a7e3e3
Compare
|
0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (25.20% Estimated after merge)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issues liées
#2541
#2543
Quel est le comportement actuel ?
Le run de merge-queue 32459083785 (PR #2537) échoue de façon intermittente sur les shards Playwright : les 4 shards (
strategy.matrix.shard: [1,2,3,4],runs-on: runner-playwright) démarrent chacun leur propre stack complète, JVM Keycloak 26 incluse, en parallèle sur un même runner. Keycloak dépasse alors le budget du healthcheck (interval 5s × retries 10= 50 s) etdocker compose upavorte avec le conteneurdso-console_keycloakenError. En cas d'échec, aucun log docker n'est remonté : le diagnostic est impossible depuis CI. Le healthcheck contient aussi une typo (fsSau lieu de-fsS).Quel est le nouveau comportement ?
max-parallel: 2sur la stratégie du job Playwright : 2 shards au plus bootent leurs stacks Keycloak simultanément, réduisant la contention CPU/RAM à l'origine du dépassement du healthcheck.Dump docker compose state on failure(stepif: failure()) :docker compose ps -a,logs --no-color keycloak, etdocker inspect dso-console_keycloak(OOMKilled/ExitCode) — pour trancher OOM vs timeout directement depuis l'échec CI.fsS→-fsSdansdocker-compose.ci.yml(hygiène ; sans effet sur le flake, la typo étant inoffensive carcurlrenvoie le code de la dernière URL).Cette PR introduit-elle un breaking change ?
Non.
Autres informations
Discussion liée : #2540. Run de référence : https://github.com/cloud-pi-native/console/actions/runs/32459083785