|
Ran
|
Jobs
12
|
Files
70
|
Run time
1min
|
Badge
README BADGES
|
push
github
[fix] Fixed devices stuck in PROBLEM status #830 Devices that failed all critical checks could remain stuck in problem status instead of being marked critical. This happened when recovery checks were triggered while the critical metric state had not changed, preventing the status from being recalculated. Closes #830 [backport 1.2] (cherry picked from commit c16d846f0)
3840 of 3895 relevant lines covered (98.59%)
11.83 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 2 |
98.87 |
0.01% | device/base/models.py |
| 2 |
96.3 |
0.14% | device/tasks.py |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | python-3.10-django~=5.2.0 - 29624756068.1 | 70 |
98.56 |
GitHub Action Run | |
| 2 | python-3.10-django~=4.2.0 - 29624756068.2 | 70 |
98.54 |
GitHub Action Run | |
| 3 | python-3.13-django~=5.2.0 - 29624756068.3 | 70 |
98.56 |
GitHub Action Run | |
| 4 | python-3.12-django~=5.2.0 - 29624756068.4 | 70 |
98.56 |
GitHub Action Run | |
| 5 | python-3.10-django~=5.1.0 - 29624756068.5 | 70 |
98.56 |
GitHub Action Run | |
| 6 | python-3.9-django~=4.2.0 - 29624756068.6 | 70 |
98.56 |
GitHub Action Run | |
| 7 | python-3.11-django~=5.1.0 - 29624756068.7 | 70 |
98.54 |
GitHub Action Run | |
| 8 | python-3.13-django~=5.1.0 - 29624756068.8 | 70 |
98.56 |
GitHub Action Run | |
| 9 | python-3.11-django~=4.2.0 - 29624756068.9 | 70 |
98.56 |
GitHub Action Run | |
| 10 | python-3.11-django~=5.2.0 - 29624756068.10 | 70 |
98.54 |
GitHub Action Run | |
| 11 | python-3.12-django~=5.1.0 - 29624756068.11 | 70 |
98.56 |
GitHub Action Run | |
| 12 | python-3.12-django~=4.2.0 - 29624756068.12 | 70 |
98.56 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|