Bug#986928: autopkgtest-virt-qemu fails with stderr: Generating grub configuration file

2021-04-15 Thread Santiago R.R.
Control: notfound -1 0.42.2-1

El 14/04/21 a las 16:18, Simon McVittie escribió:
> Control: reassign -1 src:libcgroup 0.42.2-1
> 
> On Wed, 14 Apr 2021 at 15:43:42 +0200, Santiago R.R. wrote:
> > autopkgtest [15:15:46]: test tools-cgroupv1:  - - - - - - - - - - results - 
> > - - - - - - - - -
> > tools-cgroupv1   FAIL stderr: Generating grub configuration file ...
> 
> Part of the autopkgtest specification[1] is that by default, a test
> is considered to have failed if it either exits with a nonzero status,
> *or prints anything to stderr*. Your test is exiting 0, but it prints
> (harmless) messages to stderr, so the specification says it has
> failed. autopkgtest is reporting this correctly.
> 
> I believe the intention was that checking stderr like this would make
> warnings and other suspicious things fatal by default. With hindsight,
> this was probably not the right default, but we're stuck with it now.
> 
> If this is not what you want, either mark the test with
> "Restrictions: needs-root, isolation-machine, allow-stderr", or run
> update-grub like "update-grub 2>&1" so that its diagnostic messages go to
> stdout.
...

Mmm, thanks. I think I misunderstood the behaviour of the qemu virt. I
wrongly thought it was something related with grub and autopkgtest.

Thank you, and sorry for the noise,

 -- Santiago


signature.asc
Description: PGP signature


Bug#986928: autopkgtest-virt-qemu fails with stderr: Generating grub configuration file

2021-04-14 Thread Simon McVittie
Control: reassign -1 src:libcgroup 0.42.2-1

On Wed, 14 Apr 2021 at 15:43:42 +0200, Santiago R.R. wrote:
> autopkgtest [15:15:46]: test tools-cgroupv1:  - - - - - - - - - - results - - 
> - - - - - - - -
> tools-cgroupv1   FAIL stderr: Generating grub configuration file ...

Part of the autopkgtest specification[1] is that by default, a test
is considered to have failed if it either exits with a nonzero status,
*or prints anything to stderr*. Your test is exiting 0, but it prints
(harmless) messages to stderr, so the specification says it has
failed. autopkgtest is reporting this correctly.

I believe the intention was that checking stderr like this would make
warnings and other suspicious things fatal by default. With hindsight,
this was probably not the right default, but we're stuck with it now.

If this is not what you want, either mark the test with
"Restrictions: needs-root, isolation-machine, allow-stderr", or run
update-grub like "update-grub 2>&1" so that its diagnostic messages go to
stdout.

[1] 
https://salsa.debian.org/ci-team/autopkgtest/blob/master/doc/README.package-tests.rst

smcv