|
Ran
|
Jobs
5
|
Files
87
|
Run time
1min
|
Badge
README BADGES
|
push
CirrusCI
daemon lockfile: if create_time is in the future, don't wait for it :D - if Electrum cannot do a graceful shutdown, the daemon lockfile won't get cleaned up - the daemon lockfile contains the creation time of the daemon - then, especially for an always offline phone/laptop, if the battery dies, the clock might go back to the past - the bug: next time Electrum starts, the program will wait until create_time + 1.0 before giving up on the daemon and creating a new one closes https://github.com/spesmilo/electrum/issues/9802 - certainly fixes at least https://github.com/spesmilo/electrum/issues/9802#issuecomment-3020220593 - the OP there might or might not be the same issue closes https://github.com/spesmilo/electrum/issues/9529 - same here, might or might not be the same issue the logic bug is quite old, from https://github.com/spesmilo/electrum/commit/e6020975a
0 of 6 new or added lines in 1 file covered. (0.0%)
3 existing lines in 3 files now uncovered.21958 of 36696 relevant lines covered (59.84%)
2.99 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 6 |
43.84 |
-0.26% | electrum/daemon.py |
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 1 |
43.84 |
-0.26% | electrum/daemon.py |
| 1 |
65.63 |
-0.08% | electrum/lnchannel.py |
| 1 |
57.71 |
-0.05% | electrum/lnpeer.py |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 5611871706808320.1 | 87 |
59.81 |
||
| 2 | 5611871706808320.2 | 87 |
59.79 |
||
| 3 | 5611871706808320.3 | 87 |
59.82 |
||
| 4 | 5611871706808320.4 | 87 |
59.79 |
||
| 5 | 5611871706808320.5 | 87 |
59.79 |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|