Automatically add existence tests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 24
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 17
Description
I am not sure if it is a good idea or on some platforms it slow down the build process too match (especially on windows), but it would be interesting to automatically add an existence tests for ros pkg, to early catch runtime install conflicts such as https://github.com/RoboStack/ros-jazzy/issues/125 .
At the moment, we manually add this test for some key packages:
tests:
# Regression test for https://github.com/RoboStack/ros-jazzy/issues/125
- script:
- ros2 pkg prefix desktop
but ros2 pkg prefix <rospkgnamewithoutprefix> should be true for all ROS pkgs.
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 by tracing how vinca generates the conda recipe tests section and compare it with the manually added ros2 pkg prefix desktop check shown here. Determine the package set and platform/build-time impact, then verify generated recipes include an existence check for every ROS package without adding unnecessary checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100