From corsac at debian.org Mon Apr 8 09:13:05 2024 From: corsac at debian.org (Yves-Alexis Perez) Date: Mon, 08 Apr 2024 10:13:05 +0200 Subject: [Pkg-swan-devel] Bug#1068543: Bug#1068543: strongswan: isolation-machine autopkgtest fails: starter IS NOT RUNNING In-Reply-To: <2dd55947-c8cc-4762-abc0-a04f91bd12e0@debian.org> References: <2dd55947-c8cc-4762-abc0-a04f91bd12e0@debian.org> <2dd55947-c8cc-4762-abc0-a04f91bd12e0@debian.org> Message-ID: <5402f86a0bce79b1914a501260721b347b856951.camel@debian.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Sun, 2024-04-07 at 10:39 +0200, Paul Gevers wrote: > 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. 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, - -- Yves-Alexis -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYTpxEACgkQ3rYcyPpX RFubwAf7BLanLdiDs0ERBersGiLzc0+SF2Fxid7d2k4hfANYpBNvGYuM4PHwP4Up Pizj69Ayh8tjyB0lwb0v5cnX83BLPHCVyTvIuql+HazdbnZL9/rvntPocZ9T8fr/ ecJA1X+kE3Y2Q9xhI1Q1eiCJwpkoiam3Uz4IleazoWCl/2+/cOcqRApYK7y5HGpt Jl2CD3gCNtxiY+R2ExyrzQHvdXlSPkn92gVwcrrF4G+vsiS75fKIDaPA5KQTIPHl zHNgX2Maw+kqKpc/2hQM5Hx5rMNsnU5ugFLSVov8jmgt3vXz4AuKgHQwiSfZbS2+ VBCgM/oAOtChVK3S/v8uxn4srKdfbg== =CEmc -----END PGP SIGNATURE----- From elbrus at debian.org Mon Apr 8 19:40:10 2024 From: elbrus at debian.org (Paul Gevers) Date: Mon, 8 Apr 2024 20:40:10 +0200 Subject: [Pkg-swan-devel] Bug#1068543: Bug#1068543: strongswan: isolation-machine autopkgtest fails: starter IS NOT RUNNING In-Reply-To: <5402f86a0bce79b1914a501260721b347b856951.camel@debian.org> References: <2dd55947-c8cc-4762-abc0-a04f91bd12e0@debian.org> <5402f86a0bce79b1914a501260721b347b856951.camel@debian.org> <2dd55947-c8cc-4762-abc0-a04f91bd12e0@debian.org> Message-ID: <32cfc3c8-79b9-465e-adc1-e1f3eb842ccd@debian.org> Hi Yves-Alexis, On 08-04-2024 10:13 a.m., Yves-Alexis Perez wrote: > thanks for the report. I might try to investigate a bit but at that point > honestly I don't have much clue what happens. Can we try and find out together? > Could you please provide a bit more context in the bug report so we have a bit > more data? 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. > 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. 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. > And if enabling isolation-machine breaks the test, then maybe isolation- > machine needs to be fixed, or just not enabled? 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? > I cant say for sure but it > looks like the easiest way for me. 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 495 bytes Desc: OpenPGP digital signature URL: