test: Don't collapse dmesg in CI when there's a kernel call trace

[MggMuggins]

It would have saved me some time if the dmesg hadn't been collapsed while I was chasing this kernel bug.

Not thinking of any situation where we wouldn't want to know about a call trace in the dmesg during CI.

[simondeziel]

LGTM with a tiny optional nit

[MggMuggins]

Wasn't having any luck with journalctl --grep, went back to grep -q; should be good to go now.

[simondeziel]

Wasn't having any luck with journalctl --grep, went back to grep -q; should be good to go now.

Oh, sorry about that. Works here:

$ journalctl --quiet --no-hostname --no-pager --boot=0 --lines=100 --dmesg --grep 'apparmor="DENIED" operation="open"'
Sep 23 17:12:24 kernel: audit: type=1400 audit(1727125944.612:1494): apparmor="DENIED" operation="open" class="file" profile="snap.canonical-secscan-client.secscan-client" name="/home/sdeziel/git/pylxd/" pid=84017 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Sep 23 17:12:35 kernel: audit: type=1400 audit(1727125955.505:1495): apparmor="DENIED" operation="open" class="file" profile="snap.canonical-secscan-client.secscan-client" name="/home/sdeziel/git/pylxd/" pid=84090 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

$ journalctl --quiet --no-hostname --no-pager --boot=0 --lines=100 --dmesg  | grep 'apparmor="DENIED" operation="open"'
Sep 23 17:12:24 kernel: audit: type=1400 audit(1727125944.612:1494): apparmor="DENIED" operation="open" class="file" profile="snap.canonical-secscan-client.secscan-client" name="/home/sdeziel/git/pylxd/" pid=84017 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Sep 23 17:12:35 kernel: audit: type=1400 audit(1727125955.505:1495): apparmor="DENIED" operation="open" class="file" profile="snap.canonical-secscan-client.secscan-client" name="/home/sdeziel/git/pylxd/" pid=84090 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

Oh well, whatever works :)

[MggMuggins]

Bet it would work with just --grep 'Call Trace:', I was including the kernel: prefix which I guess isn't part of what's being grepped.

[simondeziel]

Bet it would work with just --grep 'Call Trace:', I was including the kernel: prefix which I guess isn't part of what's being grepped.

Right you are, thanks!

[MggMuggins]

Updated with that change.