ci: fix bazel test suite - #3078
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b2482c1a2a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| use: { ...devices["Desktop Chrome"] }, | ||
| }, | ||
| ] | ||
| : [], |
There was a problem hiding this comment.
On any Linux Bazel worker missing a Chromium shared library, this branch removes every Playwright project; combined with --pass-with-no-tests in playground/BUILD.bazel, the target succeeds without running any of the tests under playground/tests. I reproduced that outcome in this checkout: the CLI reported Total: 0 tests in 0 files and exited 0. The identical fallback in editors/code/playwright.bazel.config.ts also silently disables the entire extension E2E suite, so missing runtime dependencies should fail the test or be supplied by the Bazel environment rather than produce a green check.
Useful? React with 👍 / 👎.
Benchmark for f3f5fcdClick to view benchmark
|
1 participant
No description provided.