fix(e2e): use separate env file for GHA tests#159
Conversation
CLI and GHA E2E suites both wrote to cli-validation.env, which can cause file collisions when tests run in parallel. Give the GHA suite its own gha-validation.env output path.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Action E2E test suite to write its output to a distinct .env file so it doesn’t conflict with the CLI E2E suite when tests run in parallel.
Changes:
- Renamed the GHA E2E env output file from
cli-validation.envtogha-validation.envine2e/gha.test.ts.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Description
Give the GHA E2E test suite its own output env file to avoid collisions with the CLI suite.
Type of Change
Changes Made
cli-validation.env→gha-validation.envine2e/gha.test.tsRoot Cause
Both CLI and GHA E2E suites wrote to the same
cli-validation.envfile, which can cause file collisions when tests run in parallel.Checklist