Closed rotu closed 3 years ago
Have you verified that this change still works on Windows with Visual Studio which is the case why this logic was added in the first place?
Working on it. How is CI normally run against ROS2 for colcon PRs?
How is CI normally run against ROS2 for colcon PRs?
The jobs on ci.ros2.org have a parameter CI_COLCON_BRANCH
to pass a branch name in the colcon
repositories. Specifying a fork isn't possible atm though.
Running CI here: https://github.com/rotu/colcon-cmake/actions/runs/222969761
Running CI here: https://github.com/rotu/colcon-cmake/actions/runs/222969761
@rotu The referenced build failed. Any update on this?
Unfortunately, no. I recommend using your regular CI --- it's clear that my attempt at using GitHub CI for this is a little half-baked.
Please see https://ci.ros2.org/job/ci_windows/12408/ which doesn't specify a build type. The test invocations fail since -C
is not specified anymore:
Test not available without configuration. (Missing "-C
"?)
I will go ahead and close this ticket for now since the approach doesn't work. Please feel free to iterate on this to support Ninja better. Either the PR can be reopened when the branch was revised or a new PR can be opened.
colcon test currently can run with the wrong build type. If
CMAKE_BUILD_TYPE
is unset, the cache line will beCMAKE_BUILD_TYPE:STRING=
, which this logic previously assumed means 'Release'. That is not a safe assumption, and in multi-config setups the configuration may be influenced byCMAKE_DEFAULT_BUILD_TYPE
,CMAKE_DEFAULT_CONFIGS
,CTEST_CONFIGURATION_TYPE
, orDEFAULT_CTEST_CONFIGURATION_TYPE
.