Skip to content

Fix TSAN report warnings for interleaved logs#6468

Open
cferreiragonz wants to merge 3 commits into
masterfrom
fix_tsan_report
Open

Fix TSAN report warnings for interleaved logs#6468
cferreiragonz wants to merge 3 commits into
masterfrom
fix_tsan_report

Conversation

@cferreiragonz

Copy link
Copy Markdown
Contributor

Description

There are multiple tests in Fast DDS that spawns new processes to test communication between different processes. Right now, every process writes its TSAN log into the same file, what might cause overlap and interleaved logs. These logs are not properly parsed by the current step in the CI in charge of analyzing them, resulting in warning ilkes:

WARNING: (2) Possible mixed report. Report header without closing the last one: 173037
WARNING: (1) Possible mixed report. Report footer without a clear header matched:

This causes certain ambiguity in the report created, as some deadlock or error might be skipped depending on the log position.

This PR targets this issue by splitting the TSAN log report in separated files per TSAN log, and then processing each file separately.

@Mergifyio backport 3.2.x 2.14.x 2.6.x

Contributor Checklist

  • Commit messages follow the project guidelines.
  • The code follows the style guidelines of this project.
  • N/A: Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
  • N/A: Any new/modified methods have been properly documented using Doxygen.
  • N/A: Any new configuration API has an equivalent XML API (with the corresponding XSD extension)
  • Changes are backport compatible: they do NOT break ABI nor change library core behavior.
  • Changes are API compatible.
  • N/A: New feature has been added to the versions.md file (if applicable).
  • N/A: New feature has been documented/Current behavior is correctly described in the documentation.
  • Applicable backports have been included in the description.

Reviewer Checklist

  • The PR has a milestone assigned.
  • The title and description correctly express the PR's purpose.
  • Check contributor checklist is correct.
  • If this is a critical bug fix, backports to the critical-only supported branches have been requested.
  • Check CI results: changes do not issue any warning.
  • Check CI results: failing tests are unrelated with the changes.

Signed-off-by: Carlos Ferreira González <carlosferreira@eprosima.com>
Signed-off-by: Carlos Ferreira González <carlosferreira@eprosima.com>
@cferreiragonz cferreiragonz added this to the v3.6.3.0 milestone Jul 8, 2026
@github-actions github-actions Bot added the ci-pending PR which CI is running label Jul 8, 2026
Signed-off-by: Carlos Ferreira González <carlosferreira@eprosima.com>
@cferreiragonz cferreiragonz requested review from richiprosima and removed request for richiprosima July 9, 2026 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-pending PR which CI is running

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant