• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

ben-manes / caffeine / #3251 / 1
100%
master: 100%

Build:
Build:
LAST BUILD BRANCH: v3.dev
DEFAULT BRANCH: master
Ran 14 Aug 2022 07:03AM UTC
Files 77
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

14 Aug 2022 06:27AM UTC coverage: 98.338% (-0.03%) from 98.364%
#3251.1

push

github-actions

ben-manes
clarify the code's intent in the ring buffers

These changes have no visible performance impact but better align to the
expected behavior, rather than being implicitly correct.

The striped buffer would return a thread contention failed status if
initializing a new ring buffer, which is preallocated with the element.
The caller only checks if appending failed due to being full, so this
change to the correct result has no effect.

The ring buffer's write counter CAS is atomic and does not require any
acquire or release memory barrier ordering upon completion. A release
fence is performed when setting the array slot, so we can piggyback on
that. While this does not impact x86 (TSO), it could have a slight
difference on a weaker memory model (e.g. ARM).

7339 of 7463 relevant lines covered (98.34%)

0.98 hits per line

Source Files on job #3251.1
  • Tree
  • List 0
  • Changed 4
  • Source Changed 3
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 3251
  • ee79f843 on github
  • Prev Job for on v3.dev (##3250.1)
  • Next Job for on v3.dev (##3255.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc