|
Ran
|
Jobs
1
|
Files
1852
|
Run time
3min
|
Badge
README BADGES
|
push
github
core/service: do not propagate reload for combined RELOADING=1 + READY=1 when notify-reload Follow-up for 3bd28bf72 SERVICE_RELOAD_SIGNAL state can only be reached via explicit reload jobs, and we have a clear distinction between that and plain RELOADING=1 notifications, the latter of which is issued by clients doing reload outside of our job engine. I.e. upon SERVICE_RELOAD_SIGNAL + RELOADING=1 we don't propagate reload jobs again, since that's done during transaction construction stage already. The handling of combined RELOADING=1 + READY=1 so far is bogus however, as it tries to propagate duplicate reload jobs. Amend this by following the logic for standalone RELOADING=1.
1 of 10 new or added lines in 1 file covered. (10.0%)
1279 existing lines in 56 files now uncovered.294184 of 409611 relevant lines covered (71.82%)
717228.6 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 9 |
64.7 |
-0.89% | src/core/service.c |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 13555867618.1 | 1852 |
71.82 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|