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/s/strongswan/testing/amd64/44893414/

126s autopkgtest [08:10:23]: test daemon: [-----------------------
126s ERROR: starter IS NOT RUNNING
126s autopkgtest [08:10:23]: test daemon: -----------------------]

Hi Paul,

thanks for the report. I might try to investigate a bit but at that point
honestly I don't have much clue what happens.

Could you please provide a bit more context in the bug report so we have a bit
more data? Because at that point I didn't really ask for anything and you're
making your problem my problem, which doesn't feel really fair, to be honest.
And if enabling isolation-machine breaks the test, then maybe isolation-
machine needs to be fixed, or just not enabled? I cant say for sure but it
looks like the easiest way for me.

Regards,

Hi Yves-Alexis,

Can we try and find out together?

What kind of context are you looking for? Your package has an
autopkgtest (which I assume was added such that it can run). It declares
a isolation-machine restriction, so until yesterday, the test was never
executed on ci.debian.net. I just realized that I could have looked at
Ubuntu too, which uses qemu already longer. The test passes there, so
we're looking for delta's.

It makes me sad that you see it like that. I had the impression I was
running ci.d.n as a service to Debian maintainers.

Enabling isolation-machine doesn't break tests. It enables more tests to
run and the test that previously didn't run now fails. Now I think we
should be interested to learn why (personally even more so because it
passes on Ubuntu's infrastructure [1]). Honestly, looking at the log it
appeared to me that the test was never tried and you simple had
forgotten to start the daemon, but given it works in Ubuntu, might this
be a race condition?

If you don't want your isolation-machine restricted tests to run, I can
trivially disable it again. I was rather hoping to fix either the test,
or the setup at ci.d.n or both.

Paul

[1] https://autopkgtest.ubuntu.com/packages/s/strongswan