Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
New
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
Low
|
Dan Streetman | ||
Bionic |
Fix Released
|
Low
|
Dan Streetman | ||
Focal |
Fix Released
|
Low
|
Dan Streetman | ||
Groovy |
Fix Released
|
Low
|
Dan Streetman | ||
Hirsute |
Fix Released
|
Low
|
Dan Streetman |
Bug Description
[Impact]
* Autopkgtest fails due to corrupted journal file
[Test Case]
* Observe autopkgtest root-unittests not failing with:
Assertion 'r >= 0' failed at src/journal/
[Where problems could occur]
* The change has no impact on the systemd binary packages. The relaxed test could hide a journal corruption problem, but it seems the corrupted journal files occur only on arm64 probably due to arm64 reboots being resets: LP: #1748280.
[Original Bug Text]
Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1:
https:/
[...]
PASS: test-journal-enum
====== test-journal-flush =======
Root directory /var/log/journal removed.
Directory /var/log/
mmap cache statistics: 739 hit, 5 miss
journal_
Assertion 'r >= 0' failed at src/journal/
FAIL: test-journal-flush (code: 134)
Aborted (core dumped)
====== test-journal-
[...]
autopkgtest [07:17:29]: @@@@@@@
timedated PASS
hostnamed PASS
localed-locale PASS
localed-x11-keymap PASS
logind PASS
unit-config PASS
storage PASS
networkd-test.py PASS
build-login PASS
boot-and-services PASS
udev PASS
root-unittests FAIL non-zero exit status 134
upstream PASS
boot-smoke PASS
systemd-fsckd PASS
Exit request sent.
[...]
Changed in systemd: | |
status: | Unknown → New |
Changed in systemd (Ubuntu Bionic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Focal): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Groovy): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Bionic): | |
importance: | Undecided → Low |
Changed in systemd (Ubuntu Focal): | |
importance: | Undecided → Low |
Changed in systemd (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Groovy): | |
importance: | Undecided → Low |
Changed in systemd (Ubuntu Focal): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Groovy): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Hirsute): | |
status: | New → In Progress |
assignee: | nobody → Dan Streetman (ddstreet) |
importance: | Undecided → Low |
Changed in systemd (Ubuntu Hirsute): | |
status: | In Progress → Fix Released |
I'm not 100% certain the upstream bug is the same, as it's in CentOS, but I suspect it is.
I added more detail on what I suspect the cause is in the upstream bug.