Skip to content

Fix CI so that build failure stops workflow#1619

Closed
SteveL-MSFT wants to merge 1 commit into
PowerShell:mainfrom
SteveL-MSFT:build-dir
Closed

Fix CI so that build failure stops workflow#1619
SteveL-MSFT wants to merge 1 commit into
PowerShell:mainfrom
SteveL-MSFT:build-dir

Conversation

@SteveL-MSFT

Copy link
Copy Markdown
Member

PR Summary

CI was incorrectly reporting when it failed. When the build isn't successful, it continues to try to package up the built binaries for CC, but the binaries aren't there since the build failed. Fix is to not have it continue with CC if the build has a failure.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR aims to ensure the Rust CI workflow stops appropriately when the build/test step fails, preventing downstream steps from attempting to package/upload artifacts that may not exist.

Changes:

  • Updates the continue-on-error behavior for the “Build and test with code coverage” step in Linux/macOS/Windows jobs.
  • Intends to prevent artifact packaging/upload from occurring when the build/test step fails.

Comment on lines 56 to 60
id: rust-tests
continue-on-error: true
continue-on-error: false
run: ./build.ps1 -Clippy -Test -CodeCoverage -ExcludePesterTests -Verbose
- name: Upload coverage data
if: always()
Comment on lines 148 to 152
id: rust-tests
continue-on-error: true
continue-on-error: false
run: ./build.ps1 -Clippy -Test -CodeCoverage -ExcludePesterTests -Verbose
- name: Upload coverage data
if: always()
Comment on lines 244 to 248
id: rust-tests
continue-on-error: true
continue-on-error: false
run: ./build.ps1 -Clippy -Test -CodeCoverage -ExcludePesterTests -Verbose
- name: Upload coverage data
if: always()
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