Control: retitle -1 nullrunner: aggregates test dependencies for different tests with .changes as input
Control: tags -1 unreproducible

Hi,

On 10/16/21 21:50, Paul Gevers wrote:
On 14-10-2021 21:17, Fab Stz wrote:
The test jobs are run from the automatic salsa-ci server. I don't know which
backend is actually used. Ci job is defined here: [4]

That seems to be relevant info. The log says they use the null runner,
but I think it runs in LXC.


Looking at this bug again, it's a bit hard to debug, as the links no longer work. So, from here on I'm reasoning only.

I suspect that in 2021 salsa-ci was starting up the lxc container and was calling autopkgtest with the null runner inside the container. The null runner will not de-install the packages that it installs (it doesn't have restore capabilities), so the test dependencies are available during the next test. Is that what you meant? Or did you really see the packages being installed again each time?

I tried to reproduce the issue, but with the following stanza, the second test passes and doesn't try to install `unknown` again.
```
Test-Command: true
Depends: unknown

Test-Command: true
Depends: hello
```

Paul

## inside a testbed:
# dpkg-buildpackage -S
# autopkgtest ../*_source.changes -- null

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to