Your message dated Fri, 24 Sep 2021 12:00:55 +0200 with message-id <[email protected]> and subject line Re: Bug#994421: cdebootstrap: failing autopkgtest on one of ci.d.n amd64 workers has caused the Debian Bug report #994421, regarding cdebootstrap: failing autopkgtest on one of ci.d.n amd64 workers to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 994421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994421 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: cdebootstrap Version: 0.7.8 Severity: serious X-Debbugs-CC: [email protected] Tags: sid bookworm User: [email protected] Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of you package on amd64 because with a recent upload of glibc the autopkgtest of cdebootstrap fails in testing. It seems to me that the failures are related to the worker that the test runs on. ci-worker13 fails, while the other workers are OK. We recently changed the setup of ci-worker13, to have /tmp/ of the host on tmpfs as that speeds up testing considerably is a lot of cases. I copied some of the output at the bottom of this report, but I'm not 100% sure that the /tmp there (the one inside the lxc testbed) *is* on tmpfs. Don't hesitate to contact us at [email protected] if you need help debugging this issue. Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---On Wed, Sep 15, 2021 at 09:50:55PM +0200, Paul Gevers wrote: > autopkgtest [19:32:51]: test sid-build: [----------------------- > E: Target disallows device special files > autopkgtest [19:32:51]: test sid-build: -----------------------] > > It was pointed out to me on IRC that this is probably caused by mounting > tmp with nodev. If it's save to do so, I'll update our hosts and check > again. In that case, sorry for the noise. So, you mount it nodev and are surprised that tests can't create device nodes? Bastian -- Fascinating is a word I use for the unexpected. -- Spock, "The Squire of Gothos", stardate 2124.5
--- End Message ---
