Skip to content

migrate to next_key #200

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

LGrishin
Copy link
Contributor

migrate to next_key

Copy link

codecov bot commented May 15, 2025

Codecov Report

Attention: Patch coverage is 37.50000% with 15 lines in your changes missing coverage. Please review.

Project coverage is 73.01%. Comparing base (fda4070) to head (4f9509c).
Report is 4 commits behind head on master.

Files with missing lines Patch % Lines
src/bin/malloc.rs 0.00% 13 Missing ⚠️
src/next.rs 66.66% 1 Missing ⚠️
src/ops.rs 85.71% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #200      +/-   ##
==========================================
- Coverage   73.20%   73.01%   -0.20%     
==========================================
  Files          16       16              
  Lines         642      641       -1     
==========================================
- Hits          470      468       -2     
- Misses        172      173       +1     

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

@0crat
Copy link

0crat commented May 16, 2025

@LGrishin It is not a good practice to name Git branches like "lgrishin-impl-benches". As per our policy, this naming convention violation incurs a -12 point penalty. For future reference, please name your branch after the ticket number you're working on, such as "199". This helps maintain consistency and clarity in our repository. Your current balance stands at -8. Let's aim for better branch naming moving forward.

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