#3252
100%

Ran 14 Aug 2022 04:57PM UTC

Jobs 1

Files 77

Run time 2s

Badge

Embed ▾

pending completion

Build # #3252

Build Type

push

github-actions

Committed by

ben-manes

Commit Message

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

Run Details

7339 of 7463 relevant lines covered (98.34%)

0.98 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	#3252.1	14 Aug 2022 04:57PM UTC	0	98.34

Source Files on build #3252

Detailed source file information is not available for this build.

ben-manes / caffeine / #3252
100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build #3252

ben-manes / caffeine / #3252 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build #3252

ben-manes / caffeine / #3252
100%

README BADGES
x