|
Ran
|
Jobs
1
|
Files
75
|
Run time
3s
|
Badge
README BADGES
|
push
CirrusCI
unconditionally raise ImportError if asserts are disabled I have reconsidered and now think that we should always hard-fail if asserts asserts are disabled. It is just easier to reason about the code knowing that asserts are evaluated. If an end-user or library user has a concrete use case where this is a problem, please open an issue and let us know. follow-up 0f541be6f 0e5464ca1
4 of 4 new or added lines in 1 file covered. (100.0%)
16860 of 29032 relevant lines covered (58.07%)
0.58 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 4858080651902976.1 | 0 |
58.07 |