Skip to content

Isolate tracing tests with private LTTng homes - #262

Open
sylvesterkaczmarek wants to merge 1 commit into
ros2:rollingfrom
sylvesterkaczmarek:isolate-parallel-lttng-tests
Open

Isolate tracing tests with private LTTng homes#262
sylvesterkaczmarek wants to merge 1 commit into
ros2:rollingfrom
sylvesterkaczmarek:isolate-parallel-lttng-tests

Conversation

@sylvesterkaczmarek

@sylvesterkaczmarek sylvesterkaczmarek commented Aug 19, 2026

Copy link
Copy Markdown

Description

Remove the serialization workaround between test_ros2trace and test_tracetools_launch by giving each package its own LTTng control state.

  • add tracetools_test.isolated_lttng_home() to create a private LTTNG_HOME
  • use session-scoped autouse fixtures in both tracing-test packages
  • stop only the private session daemon during teardown, restore the previous environment, and remove the temporary home
  • remove the false test_ros2trace dependency on test_tracetools_launch

This allows the build farm to schedule the two packages in parallel without sharing the same LTTng session daemon.

Fixes #99

Is this user-facing behavior change?

Did you use Generative AI?

Yes. AI was used to assist with tests.

Additional Information

Testing performed:

  • PYTHONPATH=tracetools_test pytest -q tracetools_test/test/test_lttng.py → 3 passed
  • Python syntax checks for the added helper and fixtures
  • package XML parsing
  • git diff --check

@mergify

mergify Bot commented Aug 19, 2026

Copy link
Copy Markdown

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@fujitatomoya

Copy link
Copy Markdown
Contributor

@sylvesterkaczmarek same here can you comply our AI guideline to disclose the information with using our PR template? and DCO is missing.

Give test_ros2trace and test_tracetools_launch separate LTTNG_HOME values so their session daemons cannot interfere when package tests overlap.

Remove the false dependency that serialized the two test packages.

Signed-off-by: Sylvester Kaczmarek <16242628+sylvesterkaczmarek@users.noreply.github.com>
@sylvesterkaczmarek
sylvesterkaczmarek force-pushed the isolate-parallel-lttng-tests branch from 1eced48 to e43d618 Compare August 20, 2026 09:03
@sylvesterkaczmarek

Copy link
Copy Markdown
Author

@fujitatomoya Done, thanks. DCO is corrected and the PR description now follows the ROS 2 template.

@fujitatomoya

Copy link
Copy Markdown
Contributor

PYTHONPATH=tracetools_test pytest -q tracetools_test/test/test_lttng.py → 3 passed

this does not add up. why only 3 tests? can you share what test command did you execute and result?

@fujitatomoya

Copy link
Copy Markdown
Contributor

@sylvesterkaczmarek btw, i saw you created other PRs, those do not comply the issue template and disclose of AI use.

@christophebedard
christophebedard self-requested a review August 27, 2026 16:42
@christophebedard christophebedard self-assigned this Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix LTTng issue with test_ros2trace and test_tracetools_launch so that they can run tracing tests in parallel

3 participants