-
Notifications
You must be signed in to change notification settings - Fork 554
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
Stuck building moveit on humble for over 2.5 hrs #3176
Comments
Super strange! If you try to increase the verbosity level by adding |
Tried running that but got an error
Instead ran this This is my output It always stays stuck at 92% or 100% |
Possibly you're low on RAM? I think 32 GB should be enough, but... Try building with just a few threads with |
Yeah, I already tried with 2 workers but it stays stuck. My system is not frozen, but the build just never finishes |
I wonder if it's possibly related to X11 related issues as described in this issue: This describes an issue with the popup window that can come up when build is completed, which may be failing to come up? Specifically, to confirm you can try colcon/colcon-ros#122 (comment) |
Description
Tried building from source. All packages built except for moveit2_tutorials. Stuck at 92% since 2 hrs 31 mins now.
ROS Distro
Humble
OS and version
Ubuntu 22.04.5
Source or binary build?
Source
If binary, which release version?
No response
If source, which branch?
No response
Which RMW are you using?
None
Steps to Reproduce
Followed tutorial and ran
colcon build --mixin release
Expected behavior
Should build the packages
Actual behavior
Stuck at moveit2_tutorials for 2 hr 31 mins
[Processing: moveit2_tutorials]
[Processing: moveit2_tutorials]
[Processing: moveit2_tutorials]
[Processing: moveit2_tutorials]
[Processing: moveit2_tutorials]
[Processing: moveit2_tutorials]
[Processing: moveit2_tutorials]
[Processing: moveit2_tutorials]
[Processing: moveit2_tutorials]
Aborted <<< moveit2_tutorials [2h 31min 33s]
Backtrace or Console output
No response
The text was updated successfully, but these errors were encountered: