Skip to content
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

YCM compilation fails due to gitlab downtime #149

Closed
traversaro opened this issue Jun 12, 2018 · 6 comments
Closed

YCM compilation fails due to gitlab downtime #149

traversaro opened this issue Jun 12, 2018 · 6 comments

Comments

@traversaro
Copy link
Member

[ 43%] Downloading file cmake/FindQCustomPlot.cmake from OVITO (The Open Visualization Tool) git repository (ref 8689fcb1fdd2e8dc748e76d54d3b77a3f87d384c)
-- Cannot download file https://gitlab.com/stuko/ovito/raw/8689fcb1fdd2e8dc748e76d54d3b77a3f87d384c/cmake/FindQCustomPlot.cmake
  Network problem or not existing file.
  CMake Error at /home/straversaro/src/ycm/build/3rdparty/CMakeFiles/3rdparty-ovito.dir/ycm_download_cmake_FindQCustomPlot_cmake_real.cmake:9 (file):
  file DOWNLOAD HASH mismatch

    for file: [/home/straversaro/src/ycm/build/3rdparty/CMakeFiles/3rdparty-ovito.dir/downloads/cmake/FindQCustomPlot.cmake]
      expected hash: [a59dd4d955a5e775270a4f2656a039ae490e03ed]
        actual hash: [da39a3ee5e6b4b0d3255bfef95601890afd80709]
             status: [22;"HTTP response code said error"].
  Retrying.

-- Cannot download file https://gitlab.com/stuko/ovito/raw/8689fcb1fdd2e8dc748e76d54d3b77a3f87d384c/cmake/FindQCustomPlot.cmake
  Network problem or not existing file.
  CMake Error at /home/straversaro/src/ycm/build/3rdparty/CMakeFiles/3rdparty-ovito.dir/ycm_download_cmake_FindQCustomPlot_cmake_real.cmake:9 (file):
  file DOWNLOAD HASH mismatch

    for file: [/home/straversaro/src/ycm/build/3rdparty/CMakeFiles/3rdparty-ovito.dir/downloads/cmake/FindQCustomPlot.cmake]
      expected hash: [a59dd4d955a5e775270a4f2656a039ae490e03ed]
        actual hash: [da39a3ee5e6b4b0d3255bfef95601890afd80709]
             status: [22;"HTTP response code said error"].
  Retrying.

CMake Error at /home/straversaro/src/ycm/build/3rdparty/CMakeFiles/3rdparty-ovito.dir/ycm_download_cmake_FindQCustomPlot_cmake.cmake:30 (message):
  Cannot download file
  https://gitlab.com/stuko/ovito/raw/8689fcb1fdd2e8dc748e76d54d3b77a3f87d384c/cmake/FindQCustomPlot.cmake


    Network problem or not existing file.
    CMake Error at /home/straversaro/src/ycm/build/3rdparty/CMakeFiles/3rdparty-ovito.dir/ycm_download_cmake_FindQCustomPlot_cmake_real.cmake:9 (file):
    file DOWNLOAD HASH mismatch

  

      for file: [/home/straversaro/src/ycm/build/3rdparty/CMakeFiles/3rdparty-ovito.dir/downloads/cmake/FindQCustomPlot.cmake]
        expected hash: [a59dd4d955a5e775270a4f2656a039ae490e03ed]
          actual hash: [da39a3ee5e6b4b0d3255bfef95601890afd80709]
               status: [22;"HTTP response code said error"]


3rdparty/CMakeFiles/3rdparty-ovito.dir/build.make:90: recipe for target '3rdparty/ovito/cmake/FindQCustomPlot.cmake' failed
make[2]: *** [3rdparty/ovito/cmake/FindQCustomPlot.cmake] Error 1
CMakeFiles/Makefile2:1298: recipe for target '3rdparty/CMakeFiles/3rdparty-ovito.dir/all' failed
make[1]: *** [3rdparty/CMakeFiles/3rdparty-ovito.dir/all] Error 2
Makefile:128: recipe for target 'all' failed
make: *** [all] Error 2
@traversaro traversaro changed the title YCM compilation fails due to network problem YCM compilation fails due to gitlab downtime Jun 12, 2018
@traversaro
Copy link
Member Author

For anyone having this problem, you can workaround by downloading the YCM version that does not download anything and build that one, i.e. https://github.com/robotology/ycm/releases/download/v0.6.0/ycm-0.6.0.dev-offline.tar.gz .

@traversaro
Copy link
Member Author

@traversaro
Copy link
Member Author

Related issue: #105 .

@traversaro
Copy link
Member Author

Another instance of Gitlab downtime: #113 .

@traversaro
Copy link
Member Author

Gitlab outage fixed, see post-mortem at https://gitlab.com/gitlab-com/infrastructure/issues/4380 .

@traversaro
Copy link
Member Author

The issue was fixed on the Gitlab side. For the long term solution (or at least mitigation) for this kind of problems, see #105 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant