public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	 openembedded-core@lists.openembedded.org
Cc: Trevor Gamblin <tgamblin@baylibre.com>,
	Anibal Limon <anibal@limonsoftware.com>
Subject: Re: [OE-core] [PATCH 1/2] oeqa/runtime/ptest: Use a timeout with command, remove disabling
Date: Sat, 07 Mar 2026 10:52:25 +0000	[thread overview]
Message-ID: <3ffcb3c8167d44ef76d9c4f633fe17b93ae2e15c.camel@linuxfoundation.org> (raw)
In-Reply-To: <DGVOBJODEHCK.15P1KY3F0CAFC@bootlin.com>

On Fri, 2026-03-06 at 12:47 +0100, Mathieu Dubois-Briand wrote:
> On Wed Mar 4, 2026 at 7:41 PM CET, Richard Purdie via lists.openembedded.org wrote:
> > A simple 'which' call doesn't need the timeout disabling. This was likely
> > a copy and paste error and can be removed.
> > 
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> >  meta/lib/oeqa/runtime/cases/ptest.py | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/meta/lib/oeqa/runtime/cases/ptest.py b/meta/lib/oeqa/runtime/cases/ptest.py
> > index 1a0782374d0..2887e136719 100644
> > --- a/meta/lib/oeqa/runtime/cases/ptest.py
> > +++ b/meta/lib/oeqa/runtime/cases/ptest.py
> > @@ -35,7 +35,7 @@ class PtestRunnerTest(OERuntimeTestCase):
> >          self.do_ptestrunner()
> >  
> >      def do_ptestrunner(self):
> > -        status, output = self.target.run('which ptest-runner', 0)
> > +        status, output = self.target.run('which ptest-runner')
> >          if status != 0:
> >              self.skipTest("No -ptest packages are installed in the image")
> >  
> 
> Hi Richard,
> 
> I believe this is causing some ptest failures on riscv64:
> 
> Traceback (most recent call last):
>   File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
>     return func(*args, **kwargs)
>            ^^^^^^^^^^^^^^^^^^^^^
>   File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
>     return func(*args, **kwargs)
>            ^^^^^^^^^^^^^^^^^^^^^
>   File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
>     return func(*args, **kwargs)
>            ^^^^^^^^^^^^^^^^^^^^^
>   File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/ptest.py", line 27, in test_ptestrunner_expectfail
>     self.do_ptestrunner()
>   File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/ptest.py", line 63, in do_ptestrunner
>     status, output = self.target.run('ptest-runner -t {} -d \"{}\"'.format(ptest_timeout, ' '.join(ptest_dirs)), timeout=int(ptest_timeout)+30)
>                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/target/ssh.py", line 98, in run
>     status, output = self._run(sshCmd, processTimeout, ignore_status, raw, ignore_ssh_fails)
>                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/target/ssh.py", line 70, in _run
>     raise AssertionError("ssh exited with status '255' for command "
> AssertionError: ssh exited with status '255' for command '['ssh', '-l', 'root', '-o', 'ServerAliveCountMax=2', '-o', 'ServerAliveInterval=30', '-o', 'UserKnownHostsFile=/dev/null', '-o', 'StrictHostKeyChecking=no', '-o', 'LogLevel=ERROR', '192.168.7.14', 'export PATH=/usr/sbin:/sbin:/usr/bin:/bin; ptest-runner -t 450 -d "/usr/lib"']': this is likely an SSH failure
> 
> Process killed - no output for 480 seconds. Total running time: 485 seconds.
> 
> Cannot run ptests without @expectedFailure as ptests are expected to fail
> WARNING: core-image-ptest-dpkg-1.0-r0 do_testimage: Can not retrieve artifacts from test target: Error while fetching compressed artifacts
> 
> And similar errors:
> 
> WARNING: core-image-ptest-coreutils-1.0-r0 do_testimage: Can not retrieve artifacts from test target: Error while fetching compressed artifacts
> Cannot run ptests without @expectedFailure as ptests are expected to fail
> 
> WARNING: core-image-ptest-gettext-1.0-r0 do_testimage: Can not retrieve artifacts from test target: Error while fetching compressed artifacts
> Cannot run ptests without @expectedFailure as ptests are expected to fail
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1182

Thanks. I think this has lead to an interesting discovery of an
additional issue in ptest-runner with buffering of logs when used non-
interactively.

I've sent a patch to ptest-runner which I believe will address this
issue.

Cheers,

Richard



  parent reply	other threads:[~2026-03-07 10:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 18:41 [PATCH 1/2] oeqa/runtime/ptest: Use a timeout with command, remove disabling Richard Purdie
2026-03-04 18:41 ` [PATCH 2/2] oeqa/runtime/ptest: Improve timeout values Richard Purdie
2026-03-06 11:47 ` [OE-core] [PATCH 1/2] oeqa/runtime/ptest: Use a timeout with command, remove disabling Mathieu Dubois-Briand
2026-03-06 14:28   ` Mathieu Dubois-Briand
2026-03-07 10:52   ` Richard Purdie [this message]
2026-03-10  2:14     ` Anibal Limon
2026-03-10  8:12       ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ffcb3c8167d44ef76d9c4f633fe17b93ae2e15c.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=anibal@limonsoftware.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tgamblin@baylibre.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox