[ Added autopkgtest maintainers to thread ]

[2019-07-09 15:11] Lorenz <lorenzo.r...@gmail.com>
> Il giorno mar 9 lug 2019 alle ore 01:52 Colin Watson <cjwat...@debian.org>
> ha scritto:
> >Is this just another instance of problems with your virtual machine not
> >having enough entropy (#912616 etc.)?
>
> It looks you are right, thanks for the tip!
>
> Dmitry, I can pass the test that include openssh-server with a command like
> (see #912087 message 118)
>
> $ autopkgtest ./runit-init_2.1.2-32_all.deb ./runit_2.1.2-32_amd64.deb
>  ./runit  \
> -- qemu --qemu-options='-object rng-random,filename=/dev/urandom,id=rng0
> -device virtio-rng-pci,rng=rng0' \
> ./debian-unstable.img

Confirmed. Your solution works.

Btw, I tried adding `haveged` and/or `rng-tools` to test build
dependency, and it does not work.

> This rely on the host having enough entropy and i'm not sure how to pass
> those options to salsa CI

Is it possible to run Qemu on Salsa at all?

As my experiments show¹, it is possible to create image with
`autopkgtest-qemu-build' with Salsa CI. It still complains
somewhat:

  ERROR: [Errno 2] No such file or directory: '/proc/mounts'
  ERROR: [Errno 2] No such file or directory: '/proc/mounts'
  ERROR: Command failed: kpartx -dsv ../autopkgtest.img.raw
  b''
  b'/proc/devices: fopen failed: No such file or directory\nFailed to set up 
list of device-mapper major numbers\nIncompatible libdevmapper 1.02.155 
(2018-12-18) and kernel driver (unknown version).\ndevice mapper prerequisites 
not met\n'

But actually running `autopkgtest` fails with following error:

  qemu-system-x86_64: terminating on signal 15 from pid 27862 (<unknown 
process>)
  <VirtSubproc>: failure: timed out on client shared directory setup

The only reference to such failure I found was #916428 (autopkgtest-qemu
worked with python-3.6, but not 3.7). Bug closed in autopkgtest=5.8;
current version is 5.10.

Just running /usr/bin/kvm fails, complaining about missing "kvm"
module³. Running with just software emulation is terribly slow.

As I see it, the best we can do is script creation of image and invoking
autopkgtest(1) with apporiate options and run this script from time to
time manually. Or I missed something better?

 ¹ https://salsa.debian.org/debian/runit/-/jobs/219656
 ² https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916428
 ³ https://salsa.debian.org/kaction/push-limits/-/jobs/219676
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Reply via email to