Dear maintainer(s),

Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to use that. However, it fails. Can you please
investigate the situation and fix it? I copied some of the output at the
bottom of this report.

The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing, but because machine-isolation
support by ci.debian.net is new I have not marked this bug as serious (yet).

More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html

https://ci.debian.net/packages/c/crash/testing/amd64/44896511/

  62s autopkgtest [09:38:12]: test live: [-----------------------
  63s Adding linux-image debug symbols.
  63s Hit:1 http://deb.debian.org/debian testing InRelease
  63s Reading package lists...
  63s Reading package lists...
  63s Building dependency tree...
  63s Reading state information...
  64s The following NEW packages will be installed:
  64s   linux-image-6.6.15-amd64-dbg
  64s 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  64s Need to get 793 MB of archives.
  64s After this operation, 5378 MB of additional disk space will be used.
  64s Get:1 http://deb.debian.org/debian testing/main amd64
linux-image-6.6.15-amd64-dbg amd64 6.6.15-2 [793 MB]
  68s Fetched 793 MB in 4s (194 MB/s)
  68s Selecting previously unselected package linux-image-6.6.15-amd64-dbg.
  68s (Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 21988 files and directories currently installed.)
  68s Preparing to unpack
.../linux-image-6.6.15-amd64-dbg_6.6.15-2_amd64.deb ...
  68s Unpacking linux-image-6.6.15-amd64-dbg (6.6.15-2) ...
152s Setting up linux-image-6.6.15-amd64-dbg (6.6.15-2) ...
152s Processing triggers for libc-bin (2.37-15) ...
153s Testing crash on live kernel
153s crash: /usr/lib/debug/boot/vmlinux-6.6.15-amd64: no .gnu_debuglink
section
153s
153s crash: /usr/lib/debug/boot/vmlinux-6.6.15-amd64: no debugging data
available
153s
153s autopkgtest [09:39:43]: test live: -----------------------]

Hi,
data available

Interestingly the test passes in unstable, stable and oldstable. So,
what's special in testing? The version of the kernel?

I triggered a test in testing with the kernel from unstable (src:linux
and src:linux-signed-amd64), it passed. So I'm guessing that this bug
could be reassigned to the kernel package and closed as it seems the
problem is fixed in unstable.

To prevent linux kernels that break the test like this from migrating to
testing in the future you might be interested to add a test that uses
the hint-testsuite-triggers restriction [1] with appropriate packages as
Depends.

Paul

[1]
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst