Repository navigation
Conversation
|
This is good to go now. All build checked locally. |
|
Please also check the #207 that happened during build. Not sure if the |
|
Finished all packs above "end of package support" - they are 615 packages that are now building on my machine. I think for linux-64 this is good to go and merge it. |
|
@Tobias-Fischer is this an issue with the sizing of the server, or something else? |
|
To be honest, I am not sure .. If you clean up the vinca_linux_64.yaml (only bumping the build number, removing all the comments of the packages that are contained in the meta-packages), I think I'd be happy to merge. |
|
I just remembered - we should probably address RoboStack/ros-noetic#477 (@traversaro) and #175 before merging. @traversaro - do you know how to change the mutex build string? |
|
We should also sync https://github.com/sonelu/ros-humble/blob/linux-64/.ci_support/conda_forge_pinnings.yaml with conda-forge |
|
I think I've addressed these points - @traversaro could you please take a look? |
|
Did a cleanup - I think I'd be happy if CI is going well. |
Everything seems fine, thanks! |
|
It seems to me that a patch is outdated: |
|
Ok, I fixed the backward_ros patch, now the following failure is on moveit: |
Fortunately the patch was superseded by moveit/moveit2#2399, so we can just drop it. |
It was superseded by moveit/moveit2#2399 .
|
New round new failing patch: |
Apparently the patch was integrated upstream in moveit/moveit2#2395, so se can drop also this one. |
…in.patch The patch was integrated upstream in moveit/moveit2#2395 .
|
New moveit failing patch: |
Again upstreamed: https://github.com/moveit/moveit2/pull/2895/files, we can remove it. |
|
Ok, now the error is: I vaguely remember something on a |
|
|
|
Yes, I think that was defined as an additional recipe in https://github.com/sonelu/ros-humble/tree/linux-64/additional_recipes, but that is not there, I do not know if @Tobias-Fischer remembers something on that. |
|
@Tobias-Fischer do you remember anything related to ros-workspace not build? No problem if not, I can look into this myself. |
|
No, sorry - I do remember that something fishy was going on, and that locally at some point I needed to manually build it as it wasn't built in the correct order automatically. So probably something deeper down that's wrong. |
|
@traversaro I don't remember having an issue building locally, but what happens if you add back |
…eason is not added
|
Thanks @sonelu ! Indeed adding |
|
After ~1 hour, there is a failure: that is strange, as
|
|
As discussed in RoboStack/vinca#65, I switched this PR to use the |
Actually I may found an easier solution in f32a8cb . |
|
See #229 |
Trigger for rebuild for:
Worked on a local built.
I'll follow with simulation and desktop as soon as I can.
Will also do a cleanup of the packages that are bottom in the recipe once we have all packages from the main versions.