zopefoundation / ZODB / 1065 / 8
76%
master: 84%

LAST BUILD BRANCH: repozo-incremental-recover
DEFAULT BRANCH: master
Ran
Files 51
Run time 3s
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
coverage: 75.566%. Remained the same
ZOPE_INTERFACE_STRICT_IRO=1 PURE_PYTHON=1

push

travis-ci

jmuchemb 
<a href="https://github.com/zopefoundation/ZODB/commit/<a class=hub.com/zopefoundation/ZODB/commit/313702023f01623520f510c87dbaad50e7586cc2">313702023<a href="https://github.com/zopefoundation/ZODB/commit/313702023f01623520f510c87dbaad50e7586cc2">&quot;&gt;Relax assertion in check_tid_ordering_w_commit test

It is pointless for lastTransaction() to block until it is allowed to
return the TID of a transaction that has just been committed, because
it may still not be the real last TID (e.g. for some storage
implementations, invalidations are received from a shared server
via the network). While invalidations are still being processed,
it&amp;#39;s fine to return immediately with the previous last TID.

This was clarified in commit </a><a class="double-link" href="https://github.com/zopefoundation/ZODB/commit/<a class="double-link" href="https://github.com/zopefoundation/ZODB/commit/4a6b0283f61427c7a2d8086a271bcdfb1cb53593">4a6b0283f</a>">4a6b0283f</a><a href="https://github.com/zopefoundation/ZODB/commit/313702023f01623520f510c87dbaad50e7586cc2">
(&quot;mvccadapter: check if the last TID changed without invalidation").

See pull request #316

6476 of 8570 relevant lines covered (75.57%)

0.76 hits per line

Source Files on job 1065.8 (ZOPE_INTERFACE_STRICT_IRO=1 PURE_PYTHON=1)