Skip to content
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

Add Lock-free Queue (backport #253) #270

Merged
merged 3 commits into from
Jan 29, 2025

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jan 29, 2025

Fixes #14


This is an automatic backport of pull request #253 done by Mergify.

(cherry picked from commit 1d66fed)
@codecov-commenter
Copy link

codecov-commenter commented Jan 29, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.72%. Comparing base (695a6c1) to head (7e0b457).
Report is 1 commits behind head on jazzy.

Additional details and impacted files
@@            Coverage Diff             @@
##            jazzy     #270      +/-   ##
==========================================
+ Coverage   69.13%   70.72%   +1.58%     
==========================================
  Files           8        9       +1     
  Lines         499      526      +27     
  Branches       86       87       +1     
==========================================
+ Hits          345      372      +27     
  Misses         99       99              
  Partials       55       55              
Flag Coverage Δ
unittests 70.72% <100.00%> (+1.58%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
include/realtime_tools/lock_free_queue.hpp 100.00% <100.00%> (ø)

@christophfroehlich christophfroehlich merged commit f891f6c into jazzy Jan 29, 2025
12 checks passed
@christophfroehlich christophfroehlich deleted the mergify/bp/jazzy/pr-253 branch January 29, 2025 21:48
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.

3 participants