[bug] corrupt artifactory package ?
See original GitHub issueCMake Error: The source directory "/home/luminar/.conan/data/ceres-solver/1.13.0/_/_/build/1ce849fddb6e45c13e3eae2053dbdd5fd92de535" does not appear to contain CMakeLists.txt
I get this error reproducible when running rm -rf ~/.conan/data/* /tmp/conan_download_cache/ && conan install ceres-solver/1.13.0@ -b ceres-solver -r luminar. Note the -r luminar, our private Artifactory.
When using -r conan-center, it works without error.
The recipes and packages get uploaded to the Artifactory whenever a CI is ran through succesfuly, via conan upload "*" --all --confirm --parallel --remote luminar, and my impression is, that somehow the upload moved some corrupt packages to Artifactory?
Environment Details (include every applicable attribute)
- Operating System+version: Ubuntu 18.04 and Win10
- Compiler+version: gcc 7 and msvc of VS19
- Conan version: 1.33.1
- Python version: 3.9 and 3.6.9
Steps to reproduce (Include if Applicable)
only happens on private repo 😞
Logs (Executed commands with output) (Include/Attach if Applicable)
C:\Python39\Scripts\conan.exe install ceres-solver/1.13.0@ -b ceres-solver -r luminar
Configuration:
[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=Visual Studio
compiler.runtime=MD
compiler.version=16
os=Windows
os_build=Windows
[options]
[build_requires]
[env]
ceres-solver/1.13.0: Forced build from source
Installing package: ceres-solver/1.13.0
Requirements
ceres-solver/1.13.0 from 'luminar' - Cache
eigen/3.3.8 from 'conan-center' - Cache
Packages
ceres-solver/1.13.0:6fbc4fb986f91680a0076262c273deb96eba56d6 - Build
eigen/3.3.8:5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9 - Cache
Installing (downloading, building) binaries...
eigen/3.3.8: Already installed!
ceres-solver/1.13.0: WARN: Build folder is dirty, removing it: C:\Users\florianb\.conan\data\ceres-solver\1.13.0\_\_\build\6fbc4fb986f91680a0076262c273deb96eba56d6
ceres-solver/1.13.0: Copying sources to build folder
ceres-solver/1.13.0: Building your package in C:\Users\florianb\.conan\data\ceres-solver\1.13.0\_\_\build\6fbc4fb986f91680a0076262c273deb96eba56d6
ceres-solver/1.13.0: Generator cmake created conanbuildinfo.cmake
ceres-solver/1.13.0: Calling build()
CMake Error: The source directory "C:/Users/florianb/.conan/data/ceres-solver/1.13.0/_/_/build/6fbc4fb986f91680a0076262c273deb96eba56d6" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
ceres-solver/1.13.0:
ceres-solver/1.13.0: ERROR: Package '6fbc4fb986f91680a0076262c273deb96eba56d6' build failed
ceres-solver/1.13.0: WARN: Build folder C:\Users\florianb\.conan\data\ceres-solver\1.13.0\_\_\build\6fbc4fb986f91680a0076262c273deb96eba56d6
ERROR: ceres-solver/1.13.0: Error in build() method, line 125
cmake = self._configure_cmake()
while calling '_configure_cmake', line 119
self._cmake.configure()
ConanException: Error 1 while executing cd C:\Users\florianb\.conan\data\ceres-solver\1.13.0\_\_\build\6fbc4fb986f91680a0076262c273deb96eba56d6 && cmake -G "Visual Studio 16 2019" -A "x64" -DCONAN_LINK_RUNTIME="/MD" -DCONAN_IN_LOCAL_CACHE="ON" -DCONAN_COMPILER="Visual Studio" -DCONAN_COMPILER_VERSION="16" -DCONAN_CXX_FLAGS="/MP24" -DCONAN_C_FLAGS="/MP24" -DBUILD_SHARED_LIBS="OFF" -DCMAKE_INSTALL_PREFIX="C:\Users\florianb\.conan\data\ceres-solver\1.13.0\_\_\package\6fbc4fb986f91680a0076262c273deb96eba56d6" -DCMAKE_INSTALL_BINDIR="bin" -DCMAKE_INSTALL_SBINDIR="bin" -DCMAKE_INSTALL_LIBEXECDIR="bin" -DCMAKE_INSTALL_LIBDIR="lib" -DCMAKE_INSTALL_INCLUDEDIR="include" -DCMAKE_INSTALL_OLDINCLUDEDIR="include" -DCMAKE_INSTALL_DATAROOTDIR="share" -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY="ON" -DCONAN_EXPORTED="1" -DLIB_SUFFIX="" -DGFLAGS="False" -DBUILD_EXAMPLES="False" -DBUILD_TESTING="False" -DBUILD_DOCUMENTATION="False" -DCUSTOM_BLAS="True" -DGLOG_PREFER_EXPORTED_GLOG_CMAKE_CONFIGURATION="False" -DEIGENSPARSE="True" -DSUITESPARSE="False" -DLAPACK="False" -DCXSPARSE="False" -DMINIGLOG="True" -DCMAKE_DISABLE_FIND_PACKAGE_TBB="True" -DTBB="False" -DOPENMP="False" -DEIGEN_PREFER_EXPORTED_EIGEN_CMAKE_CONFIGURATION="False" -DGFLAGS_PREFER_EXPORTED_GFLAGS_CMAKE_CONFIGURATION="False" -DCXX11_THREADS="False" -DCXX11="False" -DSCHUR_SPECIALIZATIONS="True" -DMSVC_USE_STATIC_CRT="False" -Wno-dev C:\Users\florianb\.conan\data\ceres-solver\1.13.0\_\_\build\6fbc4fb986f91680a0076262c273deb96eba56d6
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (13 by maintainers)
Top Results From Across the Web
Artifactory should either reject NPM packages with non ... - JFrog
Artifactory should either reject NPM packages with non-semver versions or discard the corrupted package.json. Description.
Read more >Known Issues - JFrog - JFrog Documentation
Enabling anonymous access can cause Artifactory operate in unhealthy mode, meaning that the WebUI continuously displays the message "JFrog ...
Read more >RPM repository becomes corrupt and requires re-creating
On several occasions, we have had a local RPM repository become corrupted is such away that certain packages are not able to be...
Read more >Faced issue while building Angular applications - JFrog
The main issue is that a developer can corrupt a repository on the JFrog Artifactory just by using a wrong registry url in...
Read more >How To Troubleshooting Artifactory 7.x Upgrade Issues - JFrog
key Resolution: This error occurs due to the join.key file being missing when the Artifactory service is starting up. Take a look at...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@jfaust the frequency this occured decreased over the last 2 month, but I am not sure what the reason for this was. Very probable a JFrog issue.
Thanks for following up. That means that it is not something from the Conan side, maybe we could close this issue?