-
Notifications
You must be signed in to change notification settings - Fork 182
fix: optimize disk space for lotus bootstrap tests #6194
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
Conversation
WalkthroughRe-enabled the Lotus bootstrap-checks job in CI by removing the disabling condition and added a pre-test disk‑space optimization step that runs a cleanup script on GitHub Actions runners before executing the Lotus bootstrap tests. Changes
Sequence Diagram(s)sequenceDiagram
participant GH as GitHub Actions runner
participant Script as optimize_disk_space_gh_worker.sh
participant CI as bootstrap-checks-lotus job
Note over GH,CI: Workflow triggers bootstrap-checks-lotus (now enabled)
GH->>Script: run ./scripts/optimize_disk_space_gh_worker.sh
Script->>GH: check GITHUB_ACTIONS env\nprint disk usage (before)
Script->>GH: remove large dirs & caches\nprune docker images/builders
Script->>GH: print disk usage (after)
GH->>CI: proceed to run lotus bootstrap tests
alt cleanup error
Script-->>GH: exit non-zero -> job fails
end
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Possibly related PRs
Suggested labels
Suggested reviewers
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
Comment |
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.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/workflows/forest.yml (1)
574-593: Incomplete job re-enablement: bootstrap-checks-lotus commented out in aggregation.The
bootstrap-checks-lotusjob is defined and will run for pull requests/pushes, but its status is not included in theintegration-tests-statusumbrella job due to line 649 being commented out. This means:
- The job runs independently but is not a gating check
- CI status reporting omits its result
- Inconsistent with PR objective to re-enable and fix the job
Verify this is intentional. If the job should be part of required CI checks (to validate the disk optimization fix works), uncomment line 649:
- local-devnet-check # - local-devnet-curio-check - bootstrap-checks-forest - # - bootstrap-checks-lotus + - bootstrap-checks-lotusIf intentional (e.g., only running manually for now), document this decision in the PR description.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.github/workflows/forest.yml(1 hunks)scripts/optimize_disk_space_gh_worker.sh(1 hunks)
🔇 Additional comments (1)
.github/workflows/forest.yml (1)
587-587: Verify script execution and error handling in workflow context.The script is invoked without error handling or prior validation. If the script fails or doesn't exist, the subsequent bootstrap tests will still run with potentially insufficient disk space.
Consider one of these approaches:
- Add explicit error checking to fail fast if cleanup insufficient:
- - run: ./scripts/optimize_disk_space_gh_worker.sh + - name: Optimize disk space + run: | + chmod +x ./scripts/optimize_disk_space_gh_worker.sh + ./scripts/optimize_disk_space_gh_worker.sh
- Or conditionally halt if disk space doesn't meet threshold:
# In the script or step AVAILABLE_GB=$(df /tmp | awk 'NR==2 {print $4}' | awk '{print int($1/1024/1024)}') if [[ $AVAILABLE_GB -lt 50 ]]; then echo "Insufficient disk space: ${AVAILABLE_GB}GB available" exit 1 fiAdditionally, verify that the script path is correct relative to the workflow execution context (typically repository root).
Summary of changes
Changes introduced in this pull request:
Reference issue to close (if applicable)
Closes #6168
Other information and links
Change checklist
Summary by CodeRabbit