Skip to content

Conversation

@julio-lopez
Copy link
Collaborator

@julio-lopez julio-lopez commented Sep 29, 2025

Ensure auto-maintenance errors are propagated. This also means that notifications are sent when auto-maintenance fails.
Preserve action error when closing the repository fails.

@julio-lopez julio-lopez requested a review from Copilot September 29, 2025 06:16
Copy link

Copilot AI left a comment

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 ensures that auto-maintenance and repository closing errors are properly propagated rather than being silently logged or overriding previous errors.

  • Replaces error logging with error joining to surface auto-maintenance failures
  • Preserves original action errors when repository closing fails by joining errors instead of overriding them

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@codecov
Copy link

codecov bot commented Sep 29, 2025

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.55%. Comparing base (cb455c6) to head (e02e4de).
⚠️ Report is 670 commits behind head on master.

Files with missing lines Patch % Lines
cli/app.go 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4851      +/-   ##
==========================================
+ Coverage   75.86%   76.55%   +0.68%     
==========================================
  Files         470      536      +66     
  Lines       37301    41167    +3866     
==========================================
+ Hits        28299    31514    +3215     
- Misses       7071     7607     +536     
- Partials     1931     2046     +115     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@julio-lopez julio-lopez marked this pull request as ready for review September 29, 2025 06:53
@julio-lopez julio-lopez merged commit a0a4a7b into kopia:master Sep 29, 2025
30 of 32 checks passed
@julio-lopez julio-lopez deleted the maintenance-errors branch September 29, 2025 06:55
julio-lopez added a commit to julio-lopez/kopia that referenced this pull request Oct 2, 2025
Prevent running "auto-maintenance" on snapshot create.

Ref:
- kopia#4851
julio-lopez added a commit to julio-lopez/kopia that referenced this pull request Oct 2, 2025
Prevent running "auto-maintenance" on snapshot create.

Ref:
- kopia#4851
julio-lopez added a commit that referenced this pull request Oct 2, 2025
Prevent running "auto-maintenance" on snapshot create.

Ref:
- #4851

Context: the test fails because there are concurrent "endurance"
runners and each of these advances the clock, some of them
significantly (action{Small,Medium,Large}ClockJump), which
causes the clock skewness check to fail when
(auto-)maintenance runs.

The test maintenance action does not experience this issue
because it runs exclusively on its own, that is, other
actions have to wait until maintenance completes.
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.

1 participant