:farmer: test_message_filter times out consistently in nightly Linux builds
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 153
- Forks
- 256
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 14
Description
Generated by Generative AI
No response
Operating System:
Ubuntu resolute and rhel
ROS version or commit hash:
Rolling
RMW implementation (if applicable):
No response
RMW Configuration (if applicable):
No response
Client library (if applicable):
No response
'ros2 doctor --report' output
No response
Steps to reproduce issue
- Go to any of the jobs listed below
- Build a job
- See tests failing
Expected behavior
To build without test regressions
Actual behavior
Buildiing with test regressions
Additional information
Reference Build
Failing test
- test_tf2.test_message_filter.gtest.missing_result
- projectroot.test_message_filter
Log Output
2: [ OK ] MessageFilter.noTransformsSameFrame (29 ms)
2: [ RUN ] MessageFilter.preexistingTransforms
2: [ OK ] MessageFilter.preexistingTransforms (28 ms)
2: [ RUN ] MessageFilter.postTransforms
2: [ OK ] MessageFilter.postTransforms (27 ms)
2: [ RUN ] MessageFilter.concurrentTransforms
2/7 Test #2: test_message_filter ...................***Timeout 60.06 sec
Flakyness 15 days
| job_name | last_fail | first_fail | build_count | failure_count | failure_percentage |
|---|---|---|---|---|---|
| nightly_linux-rhel_repeated | 2026-08-19 | 2026-08-04 | 16 | 16 | 100.0 |
| nightly_linux-rhel_debug | 2026-08-19 | 2026-08-05 | 16 | 10 | 62.5 |
| nightly_linux_repeated | 2026-08-18 | 2026-08-06 | 13 | 10 | 76.92 |
| nightly_linux_debug | 2026-08-18 | 2026-08-05 | 14 | 8 | 57.14 |
| nightly_linux-aarch64_repeated | 2026-08-18 | 2026-08-05 | 13 | 2 | 15.38 |
| nightly_linux-aarch64_debug | 2026-08-18 | 2026-08-05 | 16 | 8 | 50.0 |
| Rci__nightly-debug_ubuntu_resolute_amd64 | 2026-08-04 | 2026-08-04 | 2 | 1 | 50.0 |
No clear beginning
CC: @Crola1702
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the test_message_filter target and the failing test_tf2.test_message_filter.gtest.missing_result and projectroot.test_message_filter entries. Reproduce the timeout using the referenced nightly Linux jobs and inspect the concurrentTransforms stage in the log. Done means the affected Linux builds complete without this test timing out or regressing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100