All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <adrian.freihofer@siemens.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 4/8] oe-selftest: devtool ide-sdk: wait for gdbserver readiness
Date: Tue, 11 Aug 2026 10:41:10 +0200	[thread overview]
Message-ID: <DKLZAWF7WFS1.J8B4FGVB5AT3@bootlin.com> (raw)
In-Reply-To: <20260809093629.3457107-5-adrian.freihofer@siemens.com>

On Sun Aug 9, 2026 at 11:35 AM CEST, Adrian Freihofer via lists.openembedded.org wrote:
> From: Adrian Freihofer <adrian.freihofer@siemens.com>
>
> Replace the fixed delay and process-list probe for GDB background tasks
> with a wait for the readiness marker generated in tasks.json. This
> verifies the same background-task contract VS Code uses before starting
> the debugger session.
>
> Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
> ---

Hi Adrian,

I know you already discussed the issue with Richard, just adding a
comment here to keep a trace of the issue.

Before this patch we had intermittent failures of the
devtool.DevtoolIdeSdkTests.test_devtool_ide_sdk_code_cmake and
devtool.DevtoolIdeSdkTests.test_devtool_ide_sdk_code_meson tests.
Starting with this patch, the same tests are always failing:

2026-08-11 08:17:37,903 - oe-selftest - INFO - devtool.DevtoolIdeSdkTests.test_devtool_ide_sdk_code_cmake (subunit.RemotedTestCase)
2026-08-11 08:17:37,904 - oe-selftest - INFO -  ... FAIL
...
2026-08-11 08:17:37,904 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/srv/pokybuild/yocto-worker/oe-selftest-debian/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/devtool.py", line 3655, in test_devtool_ide_sdk_code_cmake
    self._verify_launch_json_debugging(tempdir, qemu, example_exe)
  File "/srv/pokybuild/yocto-worker/oe-selftest-debian/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/devtool.py", line 3527, in _verify_launch_json_debugging
    self._verify_launch_config(tempdir, config, tasks, qemu, example_exe,
  File "/srv/pokybuild/yocto-worker/oe-selftest-debian/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/devtool.py", line 3598, in _verify_launch_config
    self.assertTrue(
  File "/usr/lib/python3.11/unittest/case.py", line 715, in assertTrue
    raise self.failureException(msg)
AssertionError: False is not true : gdbserver did not report readiness on port 1234

https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/4529

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-08-11  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-09  9:35 [PATCH v2 0/8] oe-selftest: devtool ide-sdk: fix lldb connect race in _lldb_server_debugging_once AdrianF
2026-08-09  9:35 ` [PATCH v2 1/8] devtool: ide-sdk: wait for lldb-server readiness AdrianF
2026-08-09  9:35 ` [PATCH v2 2/8] oe-selftest: devtool " AdrianF
2026-08-09  9:35 ` [PATCH v2 3/8] devtool: ide-sdk: synchronize debugger server readiness AdrianF
2026-08-09  9:35 ` [PATCH v2 4/8] oe-selftest: devtool ide-sdk: wait for gdbserver readiness AdrianF
2026-08-11  8:41   ` Mathieu Dubois-Briand [this message]
2026-08-09  9:35 ` [PATCH v2 5/8] devtool: ide-sdk: wait for debugger server shutdown AdrianF
2026-08-09  9:35 ` [PATCH v2 6/8] oe-selftest: devtool ide-sdk: verify debugger shutdown AdrianF
2026-08-09  9:35 ` [PATCH v2 7/8] oe-selftest: devtool: use QEMU target commands AdrianF
2026-08-09  9:35 ` [PATCH v2 8/8] cpp-example: prevent compiler from eliminating debugger test code AdrianF

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=DKLZAWF7WFS1.J8B4FGVB5AT3@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.