#autopkgtest — Public Fediverse posts

Help! #autopkgtest LXD backend doesn't work on #debian booworm for me.
I've been following https://ci.debian.net/doc/file.MAINTAINERS.html#label-Using+the+lxc+backend and actual runs fail to prepare the testbed, crashing on:

```
<VirtSubproc>: failure: (down) ['mkdir', '-m', '777', '/tmp/autopkgtest-lxc.ghbuqhin/downtmp'] failed (exit status 1, stderr 'mkdir: cannot create directory ‘/tmp/autopkgtest-lxc.ghbuqhin/downtmp’: No such file or directory\n')
```

I had a look at the source and this makes no sense to me.

Help! #autopkgtest LXD backend doesn't work on #debian booworm for me.
I've been following https://ci.debian.net/doc/file.MAINTAINERS.html#label-Using+the+lxc+backend and actual runs fail to prepare the testbed, crashing on:

```
<VirtSubproc>: failure: (down) ['mkdir', '-m', '777', '/tmp/autopkgtest-lxc.ghbuqhin/downtmp'] failed (exit status 1, stderr 'mkdir: cannot create directory ‘/tmp/autopkgtest-lxc.ghbuqhin/downtmp’: No such file or directory\n')
```

I had a look at the source and this makes no sense to me.

If you deal with #autopkgtest then https://ci.debian.net/doc/file.MAINTAINERS.html#label-How+can+I+reproduce+the+test+run+locally-3F is very useful

If you deal with #autopkgtest then https://ci.debian.net/doc/file.MAINTAINERS.html#label-How+can+I+reproduce+the+test+run+locally-3F is very useful

Are you using #autopkgtest to check your #Debian packages?

Are you seeing hangs/timeouts when autopkgtest is copying your source tree into the qemu virtual machine?

Have a look at this snippet for a solution: https://gitlab.com/-/snippets/3714122

Are you using #autopkgtest to check your #Debian packages?

Are you seeing hangs/timeouts when autopkgtest is copying your source tree into the qemu virtual machine?

Have a look at this snippet for a solution: https://gitlab.com/-/snippets/3714122

How does one use #autopkgtest and #riscv64 virtual machines running on #qemu under amd64 on #Debian

I tried naive autopkgtest-build-qemu but it fails due to grub not having support for the architecture. Is there a better way to reproduce issues affecting RISC-V?

How does one use #autopkgtest and #riscv64 virtual machines running on #qemu under amd64 on #Debian

I tried naive autopkgtest-build-qemu but it fails due to grub not having support for the architecture. Is there a better way to reproduce issues affecting RISC-V?

Running #autopkgtest with #Docker inside Docker

To annoy my #Debian friends, I did something with a shit-ton of non-free things to make it easier to do Debian work…
(No, really, I did it because I needed it, I would never do something *just* to annoy someone 😽 )

https://www.die-welt.net/2023/04/running-autopkgtest-with-docker-inside-docker/

Finally! #Lintian's test suite passes #autopkgtest again on all architectures since Lintian version 2.116.1 — which I've released and uploaded to #Debian Unstable 1.5 days ago! https://qa.debian.org/excuses.php?package=lintian

Finally! #Lintian's test suite passes #autopkgtest again on all architectures since Lintian version 2.116.1 — which I've released and uploaded to #Debian Unstable 1.5 days ago! https://qa.debian.org/excuses.php?package=lintian

And sometimes your test suite executes properly during the build, but not during #autopkgtest testing because files present are build-time aren't all shipped in the package, meaning inconsistencies and failures down the road…

You know me, among @debian services, I tend to praise https://sources.debian.org/ and https://snapshot.debian.org/ quite often.

Today's shout-out goes to https://ci.debian.net/ which executes #autopkgtest for many archs, finding bugs I would have otherwise missed.