fix:unstable_CI

[chejinge]

Summary by CodeRabbit

• Chores
  • Updated CI workflows to aggressively free disk space before and during builds, with consistent disk-usage reporting.
  • Added targeted cleanup steps to remove interim build artifacts and test data after tests.
  • Introduced extra cleanup phases between unit and integration tests and environment-specific build configuration adjustments for more reliable runs.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Added and expanded disk-space management and cleanup steps in the CI workflow: free-disk reporting, broader artifact and dependency removal, and test-data/process teardown, with disk usage reporting after cleanup across Ubuntu and CentOS build jobs (no functional macOS changes).

Changes

Cohort / File(s)

Summary

GitHub Actions workflow \.github/workflows/pika\.yml

Added initial Free Disk Space steps; renamed Cleanup -> Cleanup Build Trees and extended to remove deps and report df -h; added Cleanup Build Artifacts to purge *.o, *.a, CMakeFiles, _deps, and other intermediate build files; added Cleanup Test Data steps using always() to stop services and remove test data/configs; introduced OS-specific cleanup expansions for Ubuntu and CentOS; added disk-usage reporting after many cleanup steps.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify cleanup paths and globs to avoid accidental removals
• Check placement and correctness of if: always() / if: ${{ always() }} semantics
• Confirm df -h reporting runs in all targeted OS runners

Suggested reviewers

• Mixficsol

Poem

🐇 I nudge the runners, clear crumbs from the tray,
Logs breathe a little easier, space finds its way,
Trees trimmed and artifacts swept from the night,
CI hums softly, all tidy and bright — hooray! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'fix:unstable_CI' is vague and uses non-descriptive formatting with a colon separator, making it unclear what specific CI issue is being addressed without reading the full changeset.	Consider using a more descriptive title that clearly states the specific problem being fixed, such as 'Fix CI disk space issues in GitHub Actions workflows' or 'Add cleanup steps to prevent disk space failures in CI builds'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0752ca1 and 2b1aae9.

📒 Files selected for processing (1)

• .github/workflows/pika.yml (6 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/pika.yml

⏰ 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). (4)

• GitHub Check: build_on_macos
• GitHub Check: build_on_centos
• GitHub Check: build_on_ubuntu
• GitHub Check: Analyze (go)

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}