ci: run e2e with Postgres and Chrome (CL-9556) - #978
Merged
Merged
Conversation
TheGreatAxios
enabled auto-merge (squash)
September 30, 2026 05:05
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.
Adds an
e2ejob to CI: pgvector/pgvector:pg16 service (the memory migration needs thevectorextension; plain postgres:16 lacks it),DATABASE_URL, a tempHUB_DATA_DIR, placeholder hub encryption keys (same values as.env.example), and Chrome via setup-chrome exported asCHROME_PATH(the name the browser harness in #973 reads). Runsbun run test:e2e(bun test e2e) withCI=true.Red suites: none. 11 tests across 3 files pass. There is no browser suite on main yet, so the Chrome step is not exercised until #973 lands.
Resolves CL-9556