It’s not a real warning, just that the print itself is issued as a warning.
I think it just needs to be issued as info instead.
Alex
On Thu 26. Aug 2021 at 11.42, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Thu, 2021-08-26 at 00:35 +0200, Alexander Kanavin wrote:
> > This is done when starting up qemu has failed, but is not done
> > when qemu started ok, but fails later in QMP communication.
> >
> > Output from runqemu does contain valuable information to find out
> > why, so rather than fix all the QMP fails to include it, let's just
> > print it in stop().
> >
> > Signed-off-by: Alexander Kanavin <alex.kana...@gmail.com>
> > ---
> > meta/lib/oeqa/utils/qemurunner.py | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/lib/oeqa/utils/qemurunner.py
> b/meta/lib/oeqa/utils/qemurunner.py
> > index 5c9d2b24a3..e099c6e2a7 100644
> > --- a/meta/lib/oeqa/utils/qemurunner.py
> > +++ b/meta/lib/oeqa/utils/qemurunner.py
> > @@ -535,6 +535,8 @@ class QemuRunner:
> > if self.runqemu.poll() is None:
> > self.logger.debug("Sending SIGKILL to runqemu")
> > os.killpg(os.getpgid(self.runqemu.pid), signal.SIGKILL)
> > + if not self.runqemu.stdout.closed:
> > + self.logger.warning("Output from runqemu:\n%s" %
> self.getOutput(self.runqemu.stdout))
> > self.runqemu.stdin.close()
> > self.runqemu.stdout.close()
> > self.runqemu_exited = True
>
> I like the idea of this but it is showing warnings on the autobuilder:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/61/builds/3877
>
> So we may need to fix the issue it is exposing?
>
> Cheers,
>
> Richard
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155344):
https://lists.openembedded.org/g/openembedded-core/message/155344
Mute This Topic: https://lists.openembedded.org/mt/85148684/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
