fix(ci): stop loading external help URL + bump Chrome to 124#6821
Open
fix(ci): stop loading external help URL + bump Chrome to 124#6821
Conversation
The web-general suite (and the Development Container smoke check that runs it) crashed Chrome with OOM when help.feature navigated the browser to https://catrobat.org/docs/. Same SHA passed 2026-05-04 and failed 2026-05-05+, so the regression was external page bloat, not code. Chromium 100 in zenika/alpine-chrome:100 (Apr 2022) cannot keep up. - Rewrite help.feature to assert the 302 + Location header via the KernelBrowser (no browser navigation, no external load). Tests the redirect we own, not the third-party page. - Add `the response Location header should be ":url"` step in ApiContext for reuse. - Bump zenika/alpine-chrome 100 -> 124 in dev/test compose so future in-app tests render on a current engine. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The previous commit returned 404 because ApiContext registers a @BeforeScenario that calls KernelBrowser::followRedirects() — once a 302 fires, the test client tries to fetch the external Location target in-app, which is not routable and 404s. Add `I do not follow redirects` step (calls followRedirects(false)) and use it before the GET so the 302 is asserted directly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
help.featuremakes the browser navigate tohttps://catrobat.org/docs/; that page apparently got heavier and Chromium 100 (zenika/alpine-chrome:100, Apr 2022, frozen) OOMs loading it. Symptom:Browser crashed,Couldn't find window,<--- Last few GCs ---> Mark-sweep ... allocation failure.help.featureto assert the 302 +Locationheader viaKernelBrowser(no real browser, no external page load). We test our own redirect, not catrobat.org's page weight. Adds a reusablethe response Location header should be ":url"step inApiContext.zenika/alpine-chrome:100→:124in bothdocker-compose.dev.yamlanddocker-compose.test.yaml. Future browser-loaded tests get a current engine instead of one stuck at 2022.Test plan
Behat (web-general web-notifications)passesDevelopment Containerpasses (runsbin/behat -s web-generalas smoke)🤖 Generated with Claude Code