-
Notifications
You must be signed in to change notification settings - Fork 29.3k
chore: Don't run integration tests twice for Turbopack #83335
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
Draft
mischnic
wants to merge
5
commits into
canary
Choose a base branch
from
mischnic/integration-tests-twice
base: canary
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
HACK comments explain environment variables that are no longer being set, creating misleading documentation.
View Details
📝 Patch Details
Analysis
Orphaned HACK Comments in GitHub Workflow
Issue Description
The GitHub workflow file
.github/workflows/build_and_test.yml
contained misleading HACK comments that referenced non-existent environment variables. These comments were remnants from a previous "cleanup" commit that removed the correspondingexport
statements but left the explanatory comments behind.Technical Analysis
Problem Manifestation
Two identical HACK comments existed at lines 405-406 and 430-431:
These comments were followed by empty lines and then the test execution commands, with no environment variable exports between them.
Root Cause
Git history analysis revealed that commit
602e541bc2
("cleanup") removed several environment variable exports including:export TURBOPACK_BUILD=1
export TURBOPACK_DEV=1
However, the commit removed the export statements but failed to remove the associated HACK comments that were explaining why these "TURBOPACK_*" variables were applicable to rspack tests despite their names.
Impact
Documentation Confusion: The orphaned comments created misleading inline documentation that referenced non-existent functionality, potentially confusing developers trying to understand the workflow configuration.
Maintenance Overhead: Future maintainers might waste time looking for the environment variables these comments referenced, or incorrectly assume variables were missing when they were intentionally removed.
Code Quality: Stale comments violate clean code principles and indicate incomplete refactoring.
Resolution
Removed both orphaned HACK comment blocks from:
test-rspack-production
jobtest-rspack-production-integration
jobThe workflow now flows directly from the rspack environment variable exports (
NEXT_RSPACK=1
,NEXT_TEST_USE_RSPACK=1
) to the test execution commands, eliminating the confusing intermediate comments that referenced nothing.Verification
TURBOPACK_BUILD
references exist anywhere in the codebase