Skip to content

ci: shard live functional tests - #76

Merged
longlho merged 6 commits into
mainfrom
codex/shard-live-functional-tests
Jul 28, 2026
Merged

ci: shard live functional tests#76
longlho merged 6 commits into
mainfrom
codex/shard-live-functional-tests

Conversation

@longlho

@longlho longlho commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • move live parity tests into e2e/live, one test per file
  • generate one Bazel js_test target per file with a Starlark loop
  • tag targets manual and functional_test
  • query functional test labels in Actions, then pass them explicitly to bazel test

Why

//e2e:live hit Bazel's 300-second timeout. Fast checks finished in about 9 seconds, while one Responses check consumed 183 seconds and blocked later coverage. Independent targets let Bazel schedule each API check concurrently and report slow failures separately.

Test

  • functional-test query returns all eight live targets
  • build all eight //e2e/live:* test targets
  • bazel test //...
  • bazel run //:gazelle -- -mode=diff
  • oxfmt --check .
  • oxlint .
  • functional run 30367577644: query selected all eight targets; 6/8 passed; Responses returned empty output and streaming Responses lacked response.completed

Comment thread .github/workflows/functional-tests.yml Outdated
PPLX_API_TOKEN: ${{ secrets.PPLX_API_TOKEN }}
run: bazel test //e2e:live --test_env=PPLX_API_TOKEN
run: |
bazel test \

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't this be //e2e/...?

@longlho
longlho marked this pull request as ready for review July 28, 2026 14:19
@longlho
longlho merged commit 074778f into main Jul 28, 2026
3 of 4 checks passed
@longlho
longlho deleted the codex/shard-live-functional-tests branch July 28, 2026 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant