-
Notifications
You must be signed in to change notification settings - Fork 52
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
Fix Windows Build Functionality #712
Fix Windows Build Functionality #712
Conversation
087f3bb
to
3dac559
Compare
* run in cmd instead of bash * disable colcon-lcov result * use --merge-install as suggessted in ros2 docs Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
3dac559
to
e8058da
Compare
@wmmc88 thanks for working on this! Do you have a map of TODOs for this? I just wanted to gauge how far along the draft was.. no rush though, just curious! |
Its been a long while since I looked at this but I think that after I fixed commands running in bash and disabled colcon-lcov result, it got further in the pipeline, but still failed at colcon test. IIRC the issue was that action-setup-ros and action-ros-ci was always using python3.7 so the colcon test command would fail. |
Actually I think it might have also been that the windows runners by default have some other python version installed and the because of the way the path was setup, IIRC, if you just comment the |
I would also be inclined to move forward with an incremental update "it builds on windows now, but the test doesn't run right", which is better than the current situation of "can't do anything on windows" |
Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
9684b8d
to
3b96a52
Compare
28bb529
to
c5d1595
Compare
Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
Can a maintainer approve builds? Builds are now all passing on my forked repo |
done! |
Codecov Report
@@ Coverage Diff @@
## master #712 +/- ##
==========================================
+ Coverage 48.38% 49.61% +1.23%
==========================================
Files 2 2
Lines 248 262 +14
Branches 58 68 +10
==========================================
+ Hits 120 130 +10
- Misses 128 132 +4
Continue to review full report at Codecov.
|
Have the mac-os tests had spurious failures before? In my fork, the action passes, but it seems to be failing in this pr due to |
not from what I remember. I re-triggered the CI jobs twice and they keep failing. From past experience, I don't think our clang macOS setup is quite right, or at least it's not exactly the same as the ROS 2 macOS CI, which might be lagging behind IIRC. Can you try re-triggering CI on your fork? |
I've re-triggered CI in my fork and it still all passes. This is a snapshot of the diff of the step that's failing on macos (Test all packages in single repo, default options): The left(ie. failing build in this fork) runner is running a newer version of clang. This is the error:
It seems like its this error: osrf/osrf_testing_tools_cpp#35 |
…ndows builds. re-enable windows for 'Test all packages in single repo, default options' step Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
…single repo, default options' test Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
c7d0a03
to
b14615a
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.
There are many little changes, but this looks good to me. I'd like to have someone else review and approve as well though.
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.
Mostly this looks good, I only have a couple requests to help make future maintenance more manageable.
Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
Signed-off-by: Melvin Wang <melvin.mc.wang@gmail.com>
done! |
@emersonknapp Could you re-review? |
Awesome! Thank you @wmmc88 and @emersonknapp ! |
FYI: It looks like the pipeline for the merged commit failed, despite it succeeding on the pr. It looks like Github recently moved windows-latest to windows server 2022. The Windows server 2022 image has [visual studio 2022] instead of 2019, which is why the build is now failing on master. Not sure what the resolution to this should be since the official docs for ros2 seem to imply it only is supported for vs2019. |
I brought up the potential move to VS 2022 recently and was told that it should be done before Humble, but it will probably require some work: ros2/ros2_documentation#2112 (comment). For now, I think we can change it to |
This action probably needs some logic to determine which version to use based off of the ros distribution then. Assuming that humble uses 2022, I assume all the older versions will only work with 2019. I think it'd be useful to document somewhere that this action needs to be run on |
Most likely.
I'll add it to the README in #719 |
Windows Test and Test-Coverage functionality will be addressed in a future pr
Signed-off-by: Melvin Wang melvin.mc.wang@gmail.com