-
Notifications
You must be signed in to change notification settings - Fork 48
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
conda Windows CI failure End of November 2023 #1542
Comments
The issue was shadowed by #1536, but the last successful CI is https://github.com/robotology/robotology-superbuild/actions/runs/6964809743 . |
This is somehow related to ami-iit/bipedal-locomotion-framework#767 . |
The error is:
The file name is |
I reproduced the problem locally with command prompt: cd C:/a/robotology-superbuild/robotology-superbuild/src/bipedal-locomotion-framework/src/YarpUtilities
C:/a/robotology-superbuild/robotology-superbuild/build/install/bin/yarpidl_thrift.exe --gen yarp --I C:/a/robotology-superbuild/robotology-superbuild/src/bipedal-locomotion-framework/src/YarpUtilities -v --out C:/a/robotology-superbuild/robotology-superbuild/build/src/bipedal-locomotion-framework/src/YarpUtilities/CMakeFiles/yarp_idl_to_dir/thrifts/BipedalLocomotion/YarpUtilities/vectorscollection thrifts/BipedalLocomotion/YarpUtilities/VectorsCollection.thrift slightly reducing the output directory path length fixes the problem. |
Even easier reproducer:
fails with:
while just removing a char from the path (even just avoiding the repeated
|
This issue will be definitely fixed by:
As robotology/yarp#3057 will take some time to be merged and released, probably we can think of a simpler solution for the CI in the short term. |
fyi @GiulioRomualdi @S-Dafarra as you may encounter this after ami-iit/bipedal-locomotion-framework#767 . |
Can we shrink the build folder path from |
Yes, I tried this in #1551 , for now just with the build to avoid having to change a lot of references to |
Interestingly @evalli-iit is experiencing this problem, but on a freshly cloned PR. |
The problem was that on his computer the long paths were not enabled https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later . |
Failure:
The text was updated successfully, but these errors were encountered: