Support abritrary epochs in TestChainstate

[jacinta-stacks]

Replaces #6608

[CLAassistant]

All committers have signed the CLA.

[codecov]

Codecov Report

❌ Patch coverage is 91.81970% with 98 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.80%. Comparing base (dc555b4) to head (8c55ee7).
⚠️ Report is 33 commits behind head on develop.

Files with missing lines	Patch %	Lines
stackslib/src/chainstate/tests/consensus.rs	94.88%	30 Missing ⚠️
stackslib/src/core/mod.rs	66.66%	19 Missing ⚠️
stacks-node/src/tests/epoch_21.rs	0.00%	16 Missing ⚠️
...-node/src/burnchains/bitcoin_regtest_controller.rs	0.00%	8 Missing ⚠️
stackslib/src/chainstate/coordinator/mod.rs	0.00%	7 Missing ⚠️
stacks-node/src/tests/epoch_205.rs	0.00%	6 Missing ⚠️
stackslib/src/chainstate/nakamoto/tests/node.rs	89.09%	6 Missing ⚠️
stackslib/src/chainstate/tests/mod.rs	99.03%	4 Missing ⚠️
...ackslib/src/chainstate/nakamoto/coordinator/mod.rs	71.42%	2 Missing ⚠️

❌ Your project status has failed because the head coverage (76.80%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@             Coverage Diff              @@
##           develop    #6619       +/-   ##
============================================
+ Coverage    64.38%   76.80%   +12.42%     
============================================
  Files          575      575               
  Lines       355807   356406      +599     
============================================
+ Hits        229097   273753    +44656     
+ Misses      126710    82653    -44057     

Files with missing lines	Coverage Δ
stacks-common/src/types/mod.rs	74.63% <100.00%> (-0.42%)	⬇️
...kslib/src/chainstate/nakamoto/coordinator/tests.rs	99.50% <100.00%> (+8.89%)	⬆️
stackslib/src/config/mod.rs	68.00% <100.00%> (+6.36%)	⬆️
stackslib/src/net/tests/mod.rs	95.78% <100.00%> (+11.15%)	⬆️
...ackslib/src/chainstate/nakamoto/coordinator/mod.rs	80.40% <71.42%> (-1.12%)	⬇️
stackslib/src/chainstate/tests/mod.rs	77.37% <99.03%> (+7.26%)	⬆️
stacks-node/src/tests/epoch_205.rs	0.00% <0.00%> (ø)
stackslib/src/chainstate/nakamoto/tests/node.rs	84.02% <89.09%> (+0.16%)	⬆️
stackslib/src/chainstate/coordinator/mod.rs	75.21% <0.00%> (-3.47%)	⬇️
...-node/src/burnchains/bitcoin_regtest_controller.rs	65.20% <0.00%> (+7.98%)	⬆️
... and 3 more

... and 368 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dc555b4...8c55ee7. Read the comment docs.

🚀 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.

[francesco-stacks]

I still need to finish the review of the changes in the consensus.rs file, but GREAT work!

[wileyj]

would have to check, but I would guess it's the tests json is not being creates successfullly. i see that step is passing, but if the json is empty it would present like this. will take a closer look tomorrow

…

On Tue, Nov 4, 2025 at 20:11 jacinta-stacks ***@***.***> wrote: *jacinta-stacks* left a comment (stacks-network/stacks-core#6619) <#6619 (comment)> Looking into all the failing tests which don't seem to like the assertions I have enforced. EDIT: not understanding why the integration tests aren't running correctly... @wileyj <https://github.com/wileyj> would you happen to know why they don't seem to want to run and just immediately fail? — Reply to this email directly, view it on GitHub <#6619 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAVXIHF2XGZ47H5FXPFRGH333F2IHAVCNFSM6AAAAACJ6CF3VCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOBYGY2TGNJYGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[federico-stacks]

lgmt!

waiting for integration test ci-process being fixed before final approval!

[aaronb-stacks]

Looks good to me, just had one question about the handling of runtime errors in the expected output struct.

[jacinta-stacks]

Looking into failing tests. These are def related to my assertions change on reward cycle setup.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.