Industrial CI CMake tests error
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the reported command in the ros2-combined-microros workspace, focusing on /root/target_ws/src/rosbot_ros/src/micro_ros_msgs and its ament copyright test. Check why CONTRIBUTING.md is expected but missing, then rerun colcon test-result --verbose; done means the micro_ros_msgs copyright test reports no failures.
Written by the indexing model from the issue text.
Description
Attaching the repository to workspace https://github.com/husarion/rosbot_ros/tree/ros2-combined-microros with industrial CI doesn't pass tests:
$ ( source /opt/ros/humble/setup.bash && cd /root/target_ws && colcon test-result --verbose; )
build/micro_ros_msgs/Testing/20231205-1159/Test.xml: 3 tests, 0 errors, 1 failure, 0 skipped
- copyright
<<< failure message
-- run_test.py: invoking following command in '/root/target_ws/src/rosbot_ros/src/micro_ros_msgs':
- /opt/ros/humble/bin/ament_copyright --xunit-file /root/target_ws/build/micro_ros_msgs/test_results/micro_ros_msgs/copyright.xunit.xml
CONTRIBUTING.md: file not found
1 errors, checked 2 files
-- run_test.py: return code 1
-- run_test.py: verify result file '/root/target_ws/build/micro_ros_msgs/test_results/micro_ros_msgs/copyright.xunit.xml'
>>>
build/micro_ros_msgs/test_results/micro_ros_msgs/copyright.xunit.xml: 2 tests, 0 errors, 1 failure, 0 skipped
- micro_ros_msgs.copyright CONTRIBUTING.md
<<< failure message
file not found
>>>
- Dominant language
- CMake
- Stars
- 15
- Forks
- 25
- Avg merge
- 16m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
Similar issues
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 65/100
lirantal/discoprint#32 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
lawndoc/stack-back#122 ·
-
ai-inspected
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
software-development-practices software-development-practices:nist-ssdf
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-cao#15860 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 68/100
Maintainers usually reply within 1 day