Repository navigation
Conversation
Coverage report
This PR does not seem to contain any modification to coverable code. |
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.
Establish a native Playwright baseline for the existing Baserow product browser suite in this fork. A fork-only branch condition enables E2E jobs even when application/test paths are unchanged. Keep the native runner, system Chrome verification, ffmpeg installation, four shards, report merger, and all unrelated CI jobs.
Scope: Chrome,
--grep-invert=@slow, 30-second timeout, three CI retries, four shards with one worker each. Preserve application image builds, database restore/migrations, and all existing Docker services. No test bodies or assertions changed.Original suite verification: completed green workflow, commit
c28553b06eb06d478fe04ccf7ef9cdaecfb5e7ca, Playwright 1.48.0. All 316 selected tests were accounted for: 305 first-attempt passes, 8 passed on retry, 3 pre-existing skips. Test-stage wall time: 464 seconds; 21 additional retry attempts, including serial-group re-execution.Playwright 1.63.0 is now pinned at commit
13fb6ee32so this native baseline matches Endform's supported version. Endform discovery hung with the 1.48 generated reporter but resolves at 1.63. The version upgrade preserves all 316 tests. The aligned native CI run completed with the entire CI Pipeline green: 311 first-attempt passes, 2 retry passes, 3 existing skips (313 executed / 316 selected; 318 total attempts). Longest shard test step: 377s (6m 17s); first test start to final test finish: 980s (16m 20s), reflecting staggered runner availability. Whole workflow: 1785s (29m 45s). E2E jobs waited 425–1083s for runners; native summed shard test-step runner time was 1194s and is not the wall-clock comparison. This aligned run is the comparison baseline.Endform migration is stacked in #2, targeting this branch. Leave this baseline PR open as reproducible evidence; do not merge it as part of the demonstration.
Separate inherited check: Database Team PR Automation fails in this fork because
DATABASE_PROJECT_WORKFLOW_TOKENis absent (Input required and not supplied: github-token). This project-board automation is unrelated to the product suite and remains unchanged.