Skip to content

[clarity-wasm-tests] stackerdb-set-signer-slots issue #6226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: feat/clarity-wasm-develop
Choose a base branch
from

Conversation

csgui
Copy link

@csgui csgui commented Jun 25, 2025

No description provided.

@csgui csgui changed the base branch from master to feat/clarity-wasm-develop June 25, 2025 15:46
@csgui csgui force-pushed the wasm-issue-666/stackerdb-set-signer-slots-issue branch from 1d73176 to 3b828bb Compare June 25, 2025 15:47
Copy link

codecov bot commented Jun 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 20.95%. Comparing base (c0fd126) to head (3b828bb).
Report is 1 commits behind head on feat/clarity-wasm-develop.

❌ Your project check has failed because the head coverage (20.95%) 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                      @@
##           feat/clarity-wasm-develop    #6226      +/-   ##
=============================================================
+ Coverage                      19.94%   20.95%   +1.00%     
=============================================================
  Files                            526      526              
  Lines                         392077   383159    -8918     
  Branches                         323      323              
=============================================================
+ Hits                           78202    80273    +2071     
+ Misses                        313867   302878   -10989     
  Partials                           8        8              
Files with missing lines Coverage Δ
...kslib/src/chainstate/nakamoto/coordinator/tests.rs 0.00% <ø> (ø)
stackslib/src/chainstate/nakamoto/tests/mod.rs 0.00% <ø> (ø)
...tackslib/src/chainstate/stacks/boot/pox_4_tests.rs 0.00% <ø> (ø)
...ckslib/src/chainstate/stacks/boot/signers_tests.rs 0.00% <ø> (ø)
stackslib/src/net/api/tests/getblock_v3.rs 0.00% <ø> (ø)
stackslib/src/net/api/tests/getblockbyheight.rs 0.00% <ø> (ø)
stackslib/src/net/api/tests/getsigner.rs 0.00% <ø> (ø)
stackslib/src/net/api/tests/gettenure.rs 0.00% <ø> (ø)
stackslib/src/net/api/tests/gettenureinfo.rs 0.00% <ø> (ø)
stackslib/src/net/api/tests/gettenuretip.rs 0.00% <ø> (ø)
... and 7 more

... and 46 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 d3d15f5...3b828bb. 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.

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