-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add colcon test verb #19
Conversation
Signed-off-by: Luca Della Vedova <lucadv@intrinsic.ai>
Signed-off-by: Luca Della Vedova <lucadv@intrinsic.ai>
Signed-off-by: Luca Della Vedova <lucadv@intrinsic.ai>
Signed-off-by: Luca Della Vedova <lucadv@intrinsic.ai>
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
Signed-off-by: Luca Della Vedova <lucadv@intrinsic.ai>
021a074
to
e80cddf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@luca-della-vedova thanks!
Closes #8
Depends on colcon/colcon-cargo#39.
I did some back and forth between whether
cargo build
should also build tests or not. In the end I settled on "no" because doing so would require passing custom arguments as shown in e80cddf.However, a
cargo build
custom command would fail if the underlying package is missing any of the required components, for example if there are no libraries or if there are no binaries.The alternative would have been to try to parse the package and generate the correct
cargo build
invocation, but that would have made the implementation fairly more complex.The implementation of the actual test takes place in
colcon-cargo
so this PR is pretty bare.