Hi Paul,

Thanks for raising this issue.

The BOOT_IMAGE issue is currently a PR upstream [1], which will be fixed
soon, and I will bring it through as soon as it is merged

With the new kmods being loaded. This is really a infra issue, and it is
difficult without being on those systems to figure these out which specific
plugin in sos is causing this issue. Ideally, I would like to solve this
issue, but without me (personally) having a reproducer, it is extremely
difficult.

I also created https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094324, a
while back, but again I couldn't reproduce this in a way that I was able to
debug the issue.

With the latter 2 issues, it seems like going to a different type of
instance, it solves the problem, hence why a restart usually works.

If I can log in and test on the different platforms Debian uses for
autopkgtest, then I can solve these issues once and for all. I always test
autopkgtest locally and salsa, and never have issues, so typically that is
my main way of affirming it is ok to publish

Let me know what resources can be available to me, for me to get this
through in a much better way

Kind Regards,
Arif

[1] https://github.com/sosreport/sos/pull/4250

---
Arif Ali

IRC: arif-ali
Matrix: @arif-ali:ubuntu.com


On Thu, 19 Nov 2026 at 18:01, Paul Gevers <[email protected]> wrote:

> Source: sos
> Version: 4.12.1-1
> Severity: serious
> User: [email protected]
> Usertags: flaky
>
> Dear maintainer(s),
>
> I looked at the results of the autopkgtest of your package because it
> showed up as blocking systemd from migrating. I noticed that it
> regularly fails on s390x and also riscv64 (but I wouldn't write this bug
> if it were only riscv64). It occasionally also fails elsewhere, it
> nearly always fails on arm64. I scheduled 8 test on s390x, 5/8 failed
> (see some examples below).
>
> Because the unstable-to-testing migration software now blocks on
> regressions in testing, flaky tests, i.e. tests that flip between
> passing and failing without changes to the list of installed packages,
> are causing people unrelated to your package to spend time on these
> tests.
>
> Don't hesitate to reach out if you need help and some more information
> from our infrastructure.
>
> Paul
>
> https://ci.debian.net/packages/s/sos/testing/s390x/78019648/
>
> 131s  (040/307)
> tests/cleaner_tests/basic_function_tests/report_with_mask.py:ReportWithUserCustomisations.test_skip_cleaning_single_file:
>
> STARTED
> 131s  (040/307)
> tests/cleaner_tests/basic_function_tests/report_with_mask.py:ReportWithUserCustomisations.test_skip_cleaning_single_file:
>
>   FAIL: Content 'BOOT_IMAGE' does not appear in
> /var/tmp/avocado_4ghr6e2ksos_tests.py.ReportWithUserCustomisations/sosreport-ReportWithUserCustomisations/sosreport-autopkgtest-incus-evhqmy-2026-11-18-sgkktrr/proc/cmdline\nroot=UUID=f54d4037-e788-419a-a4fa-20bf29f7...
>
> (0.14 s)
>
>
> https://ci.debian.net/packages/s/sos/testing/s390x/78019646/
>
> 132s  (040/307)
> tests/cleaner_tests/basic_function_tests/report_with_mask.py:ReportWithUserCustomisations.test_skip_cleaning_single_file:
>
> STARTED
> 132s  (040/307)
> tests/cleaner_tests/basic_function_tests/report_with_mask.py:ReportWithUserCustomisations.test_skip_cleaning_single_file:
>
>   FAIL: Content 'BOOT_IMAGE' does not appear in
> /var/tmp/avocado_48678pxdsos_tests.py.ReportWithUserCustomisations/sosreport-ReportWithUserCustomisations/sosreport-autopkgtest-incus-gdabgr-2026-11-18-grcnmyu/proc/cmdline\nroot=UUID=f54d4037-e788-419a-a4fa-20bf29f7...
>
> (0.17 s)
>
>
> https://ci.debian.net/packages/s/sos/testing/i386/77071180/
>
> 129s  (014/307)
> tests/cleaner_tests/report_disabled_parsers.py:ReportDisabledParsersTest.test_no_new_kmods_loaded:
>
> STARTED
> 129s  (014/307)
> tests/cleaner_tests/report_disabled_parsers.py:ReportDisabledParsersTest.test_no_new_kmods_loaded:
>
>   FAIL: Element counts were not equal:\nFirst has 0, Second has 1:
> 'sctp_diag' (0.32 s)
>

Reply via email to