304
11%
master: 80%

Ran 21 Jul 2020 08:26PM UTC

Jobs 1

Files 49

Run time 4s

Badge

Embed ▾

pending completion

Build # 304

Build Type

push

travis-ci

Committed by Spencer Kimball

Commit Message

Move from dealing with just transaction ID to using the full transaction
struct in write intents and in request / response headers.

Cleaned up some code in MVCC that was unnecessarily complex and introduced
concept of transaction epochs for Put() and for ResolveIntent(). Transaction
epochs start at 0 and are incremented every time a transaction is retried.
Transactions are retried (instead of aborted) in the event that a value is
encountered within the "window of uncertainty" between RequestHeader.Timestamp
and RequestHeader.MaxTimestamp, or in the case of an SSI transaction, if
the final transaction timestamp is not equal to the initial transaction
timestamp.

Typically, when a transaction has to restart, it covers all of the same
keys on writes and increments the intents' epochs accordingly. However,
if there's conditional logic in the transaction, it might end up skipping
some keys which were written the previous run--those earlier intents should
then not be committed when the intents are resolved after txn commit.

Run Details

110 of 993 relevant lines covered (11.08%)

0.11 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	304.1	21 Jul 2020 08:26PM UTC	0	11.08	Travis Job 304.1

Source Files on build 304

Detailed source file information is not available for this build.

cockroachdb / cockroach / 304
11%
master: 80%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 304

cockroachdb / cockroach / 304 11% master: 80%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 304

cockroachdb / cockroach / 304
11%
master: 80%

README BADGES
x