mint-components: fix CI unit test failures (Chrome sandbox + Puppeteer 22 compat) - #529
Draft
Coleton (Locrian24) with Copilot wants to merge 1 commit into
Draft
Coleton (Locrian24) with Copilot wants to merge 1 commit into
Coleton (Locrian24) with Copilot wants to merge 1 commit into
Conversation
…r 22 compat) - Add --ci to test script so Stencil launches Chrome with --no-sandbox (fixes "No usable sandbox" failure on current GitHub runners) - Patch @stencil/core 2.4.0 testing module for puppeteer 22 compat: ElementHandle.executionContext() -> .realm, Array.from for property map - Update sqm-big-stat e2e: invalid stat-type renders "-" (not "!!!") Co-authored-by: Locrian24 <46334079+Locrian24@users.noreply.github.com>
Copilot
AI
changed the title
mint-components: fix unit test CI failures (Chrome sandbox + Puppeteer 22 compat)
mint-components: fix CI unit test failures (Chrome sandbox + Puppeteer 22 compat)
Aug 27, 2026
Copilot created this pull request from a session on behalf of
Coleton (Locrian24)
August 27, 2026 18:44
View session
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
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.
The
Unit TestsCI job fails onbuild (mint-components): Puppeteer's Chrome crashes on launch withNo usable sandbox!, so no tests run. Underneath that, the Stencil 2.4 e2e harness is incompatible with the lockfile'spuppeteer@22.10.0, and one stale e2e assertion surfaced once tests could execute.Changes
package.json— pass--cito the test script. Stencil only adds--no-sandbox,--disable-setuid-sandbox, and--disable-dev-shm-usageto Chrome's launch args in CI mode; current runner kernels deny the SUID sandbox without them.patches/@stencil+core+2.4.0.patch— extend the existing patch-package patch to bridge the Puppeteer 22 API break:ElementHandle.executionContext()was removed, andevaluate*no longer unwraps arrays of element handles. Replaced withhandle.realm(verified to accept element-handle args) andArray.from(...)around the property-map iteration infindAll. Applied automatically via the existingpostinstallhook.sqm-big-stat.e2e.ts—hasInvalidStatnow expects"-"instead of"!!!". The component's invalid-stat sentinel changed at some point; the negative-path tests were never updated (confirmed against the live DOM).Suite result before: browser launch crash, 0 tests executed. After: 6/6 suites, 103/103 tests pass.