1
92%
master: 92%

Ran 22 Nov 2019 08:07PM UTC

Files 218

Run time 37s

Badge

Embed ▾

Committed 22 Nov 2019 07:56PM UTC coverage: 91.695% (-0.03%) from 91.725%

Job # 1450.1

Build Type

Pull #386

travis-ci

Committed by

web-flow

Commit Message

Fix #385 by eliminating the multiple result sets for lock_objects_and_detect_conflicts

It turns out the root of the problem was that there's no way to
reliably know whether we need to, or even can, go around the event
loop to get the second and subsequent result sets. And previously, it
could either be the first result set or the second result set that
blocked taking locks.

Now there's only one result set, so our normal way of waiting for IO
to arrive works.

Also throws in some minor optimizations targeted to avoiding extra
trips around the event loop.

Pull Request Pull Request #386: Fix #385 by eliminating the multiple result sets for lock_objects_and

Run Details

18360 of 20023 relevant lines covered (91.69%)

0.92 hits per line

zodb / relstorage / 1450 / 1
92%
master: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1450.1

zodb / relstorage / 1450 / 1 92% master: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1450.1

zodb / relstorage / 1450 / 1
92%
master: 92%

README BADGES
x