Skip to content

Revert "svm repo split: fork metrics (#7442)"#7806

Merged
steviez merged 1 commit intoanza-xyz:masterfrom
buffalojoec:revert-svm-metrics-crate
Aug 31, 2025
Merged

Revert "svm repo split: fork metrics (#7442)"#7806
steviez merged 1 commit intoanza-xyz:masterfrom
buffalojoec:revert-svm-metrics-crate

Conversation

@buffalojoec
Copy link
Copy Markdown

This reverts commit c278df4.

@buffalojoec buffalojoec requested a review from steviez August 30, 2025 13:59
@buffalojoec buffalojoec requested a review from a team as a code owner August 30, 2025 13:59
@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Aug 30, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.1%. Comparing base (c820031) to head (5e3a245).
⚠️ Report is 2311 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff            @@
##           master    #7806    +/-   ##
========================================
  Coverage    83.0%    83.1%            
========================================
  Files         812      808     -4     
  Lines      356848   356068   -780     
========================================
- Hits       296453   295919   -534     
+ Misses      60395    60149   -246     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown

@steviez steviez left a comment

Choose a reason for hiding this comment

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

:shipit:

@steviez steviez merged commit d7fdc8b into anza-xyz:master Aug 31, 2025
54 checks passed
@steviez steviez added the v3.0 label Sep 2, 2025
@mergify
Copy link
Copy Markdown

mergify Bot commented Sep 2, 2025

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.

mergify Bot pushed a commit that referenced this pull request Sep 2, 2025
This reverts commit c278df4.

(cherry picked from commit d7fdc8b)

# Conflicts:
#	Cargo.lock
#	Cargo.toml
#	programs/sbf/Cargo.lock
steviez pushed a commit that referenced this pull request Sep 3, 2025
This reverts commit c278df4.

(cherry picked from commit d7fdc8b)

# Conflicts:
#	Cargo.lock
#	Cargo.toml
#	programs/sbf/Cargo.lock
steviez added a commit that referenced this pull request Sep 4, 2025
… (#7824)

This reverts commit c278df4.

(cherry picked from commit d7fdc8b)

# Conflicts:
#	Cargo.lock
#	Cargo.toml
#	programs/sbf/Cargo.lock

---------

Co-authored-by: Joe C <joe.caulfield@anza.xyz>
Co-authored-by: steviez <steven@anza.xyz>
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.

5 participants