Skip to content

ci: should not continue on build error#1613

Merged
colinaaa merged 1 commit intolynx-family:mainfrom
colinaaa:colin/0827/build-error
Aug 27, 2025
Merged

ci: should not continue on build error#1613
colinaaa merged 1 commit intolynx-family:mainfrom
colinaaa:colin/0827/build-error

Conversation

@colinaaa
Copy link
Copy Markdown
Collaborator

@colinaaa colinaaa commented Aug 27, 2025

Summary by CodeRabbit

  • Chores
    • Strengthened CI build enforcement: build failures now block subsequent steps. This improves reliability by preventing artifacts from being produced after a failed build, surfaces issues earlier, and provides clearer failure signals. Users can expect a more predictable release process and higher confidence in build quality, with faster feedback for contributors.

Fix an regression of #1607

Checklist

  • Tests updated (or not required).
  • Documentation updated (or not required).
  • Changeset added, and when a BREAKING CHANGE occurs, it needs to be clearly marked (or not required).

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Aug 27, 2025

⚠️ No Changeset found

Latest commit: 0ac5114

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Aug 27, 2025

📝 Walkthrough

Walkthrough

Removed continue-on-error from the Build step in the build-all job of .github/workflows/workflow-build.yml, making build failures stop the job and skip subsequent steps.

Changes

Cohort / File(s) Summary
CI workflow error handling
.github/workflows/workflow-build.yml
Removed continue-on-error: true from the Build step (id: build) in build-all, changing failures from non-fatal to fatal and preventing later steps (e.g., uploading turbo summary) after a failed build.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • PupilTong

Poem

I nibbled the YAML, crisp and neat,
Snipped “continue-on-error” for a sterner beat.
If builds now stumble, we pause the run—
No hopping ahead till the work is done.
Thump-thump goes QA, ears up high—
A bunny of CI, chasing fails that fly. 🐇🚦


📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between d3989e4 and 0ac5114.

📒 Files selected for processing (1)
  • .github/workflows/workflow-build.yml (0 hunks)
💤 Files with no reviewable changes (1)
  • .github/workflows/workflow-build.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 / Build (Windows)
  • GitHub Check: build / Build (Ubuntu)
  • GitHub Check: test-rust / Test (Ubuntu)
  • GitHub Check: CodeQL Analyze (javascript-typescript)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@codecov
Copy link
Copy Markdown

codecov bot commented Aug 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@relativeci
Copy link
Copy Markdown

relativeci bot commented Aug 27, 2025

Web Explorer

#4630 Bundle Size — 368.23KiB (0%).

0ac5114(current) vs d3989e4 main#4625(baseline)

Bundle metrics  no changes
                 Current
#4630
     Baseline
#4625
No change  Initial JS 144.31KiB 144.31KiB
No change  Initial CSS 31.84KiB 31.84KiB
No change  Cache Invalidation 0% 0%
No change  Chunks 8 8
No change  Assets 8 8
No change  Modules 221 221
No change  Duplicate Modules 17 17
No change  Duplicate Code 3.85% 3.85%
No change  Packages 4 4
No change  Duplicate Packages 0 0
Bundle size by type  no changes
                 Current
#4630
     Baseline
#4625
No change  JS 236.23KiB 236.23KiB
No change  Other 100.16KiB 100.16KiB
No change  CSS 31.84KiB 31.84KiB

Bundle analysis reportBranch colinaaa:colin/0827/build-errorProject dashboard


Generated by RelativeCIDocumentationReport issue

@relativeci
Copy link
Copy Markdown

relativeci bot commented Aug 27, 2025

React Example

#4637 Bundle Size — 237.06KiB (0%).

0ac5114(current) vs d3989e4 main#4632(baseline)

Bundle metrics  no changes
                 Current
#4637
     Baseline
#4632
No change  Initial JS 0B 0B
No change  Initial CSS 0B 0B
No change  Cache Invalidation 0% 0%
No change  Chunks 0 0
No change  Assets 4 4
No change  Modules 158 158
No change  Duplicate Modules 64 64
No change  Duplicate Code 45.83% 45.83%
No change  Packages 2 2
No change  Duplicate Packages 0 0
Bundle size by type  no changes
                 Current
#4637
     Baseline
#4632
No change  IMG 145.76KiB 145.76KiB
No change  Other 91.3KiB 91.3KiB

Bundle analysis reportBranch colinaaa:colin/0827/build-errorProject dashboard


Generated by RelativeCIDocumentationReport issue

@codspeed-hq
Copy link
Copy Markdown

codspeed-hq bot commented Aug 27, 2025

CodSpeed Performance Report

Merging #1613 will not alter performance

Comparing colinaaa:colin/0827/build-error (0ac5114) with main (d3989e4)

Summary

✅ 10 untouched benchmarks

@colinaaa colinaaa merged commit d70efba into lynx-family:main Aug 27, 2025
69 of 73 checks passed
@colinaaa colinaaa deleted the colin/0827/build-error branch August 27, 2025 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants