-
Notifications
You must be signed in to change notification settings - Fork 11.4k
test: flaky unit test #26310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: flaky unit test #26310
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 1 file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 issue found across 1 file (changes from recent commits).
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name=".github/workflows/pr.yml">
<violation number="1" location=".github/workflows/pr.yml:4">
P1: Removing `pull_request_review` trigger breaks the external contributor approval workflow. The trust-check job relies on this trigger to re-run CI after a maintainer approves an external contributor's PR. Without it, external PRs will remain blocked even after approval.
Additionally, references to `github.event_name == 'pull_request_review'` in concurrency and trust-check conditions are now dead code since this event will never trigger the workflow.
If intentionally removing this flow, also clean up the dead code references to `pull_request_review` in the concurrency group, cancel-in-progress, and trust-check job.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
|
Found 3 test failures on Blacksmith runners: Failures
|
E2E results are ready! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 1 file
6c08279 to
8adb6d3
Compare
Remove node_modules from cache path in action.yml
Updated mocks for various services and constants in tests, ensuring accurate behavior for both hosted and self-hosted scenarios.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 issue found across 1 file (changes from recent commits).
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="packages/trpc/server/routers/viewer/organizations/intentToCreateOrg.handler.test.ts">
<violation number="1">
P1: `vi.mock()` inside `beforeEach()` won't work as intended. Vitest hoists `vi.mock()` calls to the top of the file at compile time, so placing it inside `beforeEach()` doesn't dynamically change the mock per describe block. The mock is set once at module load time.
For per-describe mock variations, use `vi.doMock()` (which is not hoisted) with dynamic imports, or export the constant through a getter function that can be mocked with `vi.spyOn()`/`vi.mocked().mockReturnValue()`.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Summary by cubic
Updated intentToCreateOrg tests with explicit mocks to reduce flakes and cover hosted/self-hosted flows.
Written for commit bc488f8. Summary will update on new commits.