Bug#1078424: nvidia-cuda-samples: autopkgtest needs update for new version of linux
Paul Gevers
elbrus at debian.org
Sat Aug 10 08:55:40 BST 2024
Source: nvidia-cuda-samples
Version: 12.2~dfsg-1
Severity: serious
Tags: sid trixie
User: debian-ci at lists.debian.org
Usertags: needs-update
Control: affects -1 src:linux
Dear maintainer(s),
With a recent upload of linux the autopkgtest of nvidia-cuda-samples
fails in testing when that autopkgtest is run with the binary packages
of linux from unstable. It passes when run with only packages from
testing. In tabular form:
pass fail
linux from testing 6.10.3-1
nvidia-cuda-samples from testing 12.2~dfsg-1
all others from testing from testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of linux to testing
[1]. Of course, linux shouldn't just break your autopkgtest (or even
worse, your package), but linux is too much at the core of our
infrastructure that we want to wait for updates of packages like
nvidia-cuda-samples in contrib that seem to need too often be in
lockstep. Is it possible to make the autopkgtest skip the test
(restriction skipable with exit code 77) if a too new kernel is
installed? Such that you can still see the difference between PASS and
NEUTRAL for linux kernels and hence not blocking src:linux, while at the
same time still have it failing on other regressions and thus blocking
those from migrating?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=linux
https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvidia-cuda-samples/50072469/log.gz
1722s Processing triggers for libc-bin (2.39-6) ...
1722s Processing triggers for initramfs-tools (0.142) ...
1722s update-initramfs: Generating /boot/initrd.img-6.10.3-rt-amd64
1722s W: No zstd in /usr/bin:/sbin:/bin, using gzip
1739s I: Testing binary package nvidia-fs-dkms
1739s I: Trying to install build dependency nvidia-current/535.183.01
for 6.10.3-amd64
1739s Sign command: /lib/modules/6.10.3-amd64/build/scripts/sign-file
1739s Signing key: /var/lib/dkms/mok.key
1739s Public certificate (MOK): /var/lib/dkms/mok.pub
1739s Certificate or key are missing, generating self signed certificate
for MOK...
1739s Creating symlink /var/lib/dkms/nvidia-current/535.183.01/source ->
/usr/src/nvidia-current-535.183.01
1740s 1740s Building module:
1740s Cleaning build area...
1790s Building module(s)...................(bad exit status: 2)
1790s Failed command:
1790s env NV_VERBOSE=1 make -j64 modules KERNEL_UNAME=6.10.3-amd64
1790s Error! Bad return status for module build on kernel: 6.10.3-amd64
(x86_64)
1790s Consult /var/lib/dkms/nvidia-current/535.183.01/build/make.log for
more information.
1791s autopkgtest [23:37:24]: test dkms-autopkgtest-nvidia-fs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-nvidia-devel/attachments/20240810/4a8bb0d4/attachment.sig>
More information about the pkg-nvidia-devel
mailing list