Rewrite Executor stress test
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 805
- Forks
- 564
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 27
Description
There was a stress test of the executor implementation introduced in: https://github.com/ros2/rclcpp/pull/2187 and removed via: https://github.com/ros2/rclcpp/pull/2206
It wasn't conclusive if the test implementation was the issue. I believe that we need to be exercising the executors in this way, but I'm not sure if the test here was the correct way to do it (given CI issues).
This test, or a rewrite of the test should be re-added to cover these use cases.
Contributor guide
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
Review the stress-test implementation introduced in PR 2187 and the removal in PR 2206 to understand the executor use cases and the CI problems. Rework or re-add a test that exercises those use cases reliably; done means the executor stress coverage is restored without reproducing the earlier CI issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100