Ran
|
Jobs
5
|
Files
51
|
Run time
6min
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
<a href="https://github.com/zopefoundation/ZODB/commit/<a class=hub.com/zopefoundation/ZODB/commit/4aa6218584edc7412ed24470977c7b86243c61cf">4aa621858<a href="https://github.com/zopefoundation/ZODB/commit/4aa6218584edc7412ed24470977c7b86243c61cf">">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&#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/4aa6218584edc7412ed24470977c7b86243c61cf"> ("mvccadapter: check if the last TID changed without invalidation"). See pull request #316
6457 of 8543 relevant lines covered (75.58%)
3.78 hits per line
Lines | Coverage | ∆ | File |
---|---|---|---|
1 |
90.31 |
-0.18% | src/ZODB/blob.py |
6 |
91.07 |
-3.57% | src/ZODB/utils.py |
17 |
76.47 |
-20.0% | src/ZODB/_compat.py |
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
2 | 1069.2 (ZOPE_INTERFACE_STRICT_IRO=1) | 51 |
75.55 |
Travis Job 1069.2 | |
3 | 1069.3 (ZOPE_INTERFACE_STRICT_IRO=1) | 51 |
75.51 |
Travis Job 1069.3 | |
4 | 1069.4 (ZOPE_INTERFACE_STRICT_IRO=1) | 51 |
75.51 |
Travis Job 1069.4 | |
5 | 1069.5 (ZOPE_INTERFACE_STRICT_IRO=1) | 51 |
75.59 |
Travis Job 1069.5 | |
8 | 1069.8 (ZOPE_INTERFACE_STRICT_IRO=1 PURE_PYTHON=1) | 51 |
75.57 |
Travis Job 1069.8 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|