Skip to content

[25633] Avoid using latency_data_in_ when using loans in LatencyTestPublisher (backport #6536) - #6538

Open
mergify[bot] wants to merge 2 commits into
3.2.xfrom
mergify/bp/3.2.x/pr-6536
Open

mergify[bot] wants to merge 2 commits into
3.2.xfrom
mergify/bp/3.2.x/pr-6536

Conversation

@mergify

@mergify mergify Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Description

This is a follow-up of #6531, since we are still getting a SEGV in LatencyTestPublisher.

@Mergifyio backport 3.2.x

Contributor Checklist

  • Commit messages follow the project guidelines.

  • The code follows the style guidelines of this project.

  • 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.
  • N/A: 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.

This is an automatic backport of pull request #6536 done by [Mergify](https://mergify.com).

…er (#6536)

Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
(cherry picked from commit f637688)

# Conflicts:
#	test/performance/latency/LatencyTestPublisher.cpp
@mergify mergify Bot added the conflicts Backport PR wich git cherry pick failed label Sep 18, 2026
@mergify

mergify Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor Author

Cherry-pick of f637688 has failed:

On branch mergify/bp/3.2.x/pr-6536
Your branch is up to date with 'origin/3.2.x'.

You are currently cherry-picking commit f637688.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   test/performance/latency/LatencyTestPublisher.cpp

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@MiguelCompany MiguelCompany removed the conflicts Backport PR wich git cherry pick failed label Sep 18, 2026
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
@MiguelCompany
MiguelCompany force-pushed the mergify/bp/3.2.x/pr-6536 branch from fc7bb85 to 677da6b Compare September 18, 2026 07:09
@MiguelCompany
MiguelCompany self-requested a review September 18, 2026 07:09
@MiguelCompany MiguelCompany added this to the v3.2.6 milestone Sep 18, 2026
@github-actions github-actions Bot added the ci-pending PR which CI is running label Sep 18, 2026
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