|
Repo Added
|
Files
145
|
Badge
README BADGES
|
gitlab-ci
fix: Handle first timestamp in deployment logs more carefully Depending on the system and build configuration, the timestamps in logs can use lower (likely) or higher (unlikely) time resolution than expected (nanoseconds). So in case of a deployment failure with corrupted logs, when using the first timestamp as a replacement in the extra `(THE ORIGINAL LOGS CONTAINED INVALID ENTRIES)` log entry, care must be taken to make sure the extra log entry still has a valid timestamp and that the result is valid JSON. Ticket: MEN-9427 Changelog: commit Signed-off-by: Vratislav Podzimek <vratislav.podzimek+auto-signed@northern.tech> (cherry picked from commit 1f83b7d5e)
8 of 8 new or added lines in 1 file covered. (100.0%)
7512 of 9908 relevant lines covered (75.82%)
13697.86 hits per line
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|
| Builds | Branch | Commit | Type | Ran | Committer | Via | Coverage |
|---|---|---|---|---|---|---|---|
| 2410543899 | pr_1917 | fix: Handle first timestamp in deployment logs more carefully Depending on the system and build configuration, the timestamps in logs can use lower (likely) or higher (unlikely) time resolution than expected (nanoseconds). So in case of a deploym... | Pull #1917 | gitlab-ci |
75.82 |