Re: [OE-core] [PATCH] ptest-runner: Pull in sync fix to improve log warnings

2023-06-28 Thread Richard Purdie
On Wed, 2023-06-28 at 16:24 +0200, Alexander Kanavin wrote: > This appears to have regressed glib-2.0 ptest, particularly: > Failed ptests: > {'glib-2.0': ['glib/codegen.py.test']} > https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/5273/steps/12/logs/stdio > > I didn't yet got to

Re: [OE-core] [PATCH] ptest-runner: Pull in sync fix to improve log warnings

2023-06-28 Thread Alexander Kanavin
There's an open issue for it as well: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15154 Alex On Wed, 28 Jun 2023 at 16:24, Alexander Kanavin via lists.openembedded.org wrote: > > This appears to have regressed glib-2.0 ptest, particularly: > Failed ptests: > {'glib-2.0': ['glib/codegen.py.

Re: [OE-core] [PATCH] ptest-runner: Pull in sync fix to improve log warnings

2023-06-28 Thread Alexander Kanavin
This appears to have regressed glib-2.0 ptest, particularly: Failed ptests: {'glib-2.0': ['glib/codegen.py.test']} https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/5273/steps/12/logs/stdio I didn't yet got to the root cause, just wanted to register where it happened. Note that the

[OE-core] [PATCH] ptest-runner: Pull in sync fix to improve log warnings

2023-06-18 Thread Richard Purdie
Pulls in: utils: Ensure buffers are flushed after child exits We currently wait for the child to exit but we don't flush the buffers. This can mean the output ends up out of sync and the END: line isn't at the end of the logs. We've recently seen a lot of issues related to th