[bug] Strange CI issue with test packages
See original GitHub issueI have just encountered a very strange CI issue in our build. The error output is:
14:19:18  hdf5/1.8.21@user/stable: WARN: Forced CMake build type ('Debug') different from the settings build type ('None')
14:19:18  hdf5/1.8.21@user/stable: WARN: Forced CMake build type ('Release') different from the settings build type ('None')
14:19:18  ERROR: Something failed while testing 'hdf5/1.8.21@user/stable' test_package after it was built using the lockfile. Please report this error: 'NoneType' object has no attribute 'name'
14:19:18  Command 'conan create --lockfile conan.lock packages/hdf5/all hdf5/1.8.21@user/stable' has failed
What we do is to build a set of packages that are required when users want to build our apps.
Locally, it works just fine. But on the CI, there is no build folder created inside the test_package folder, and the whole behavior seems strange. Also there is obviously no build output.
This is the test_package recipe:
from conans import ConanFile, tools, CMake
class Hdf5TestConan(ConanFile):
    settings = "os", "compiler", "arch"
    generators = "cmake_paths"
    build_requires = "cmake/[>= 3.14.0]@user/stable"
    cmake = {}
    python_requires = "helper/0.0.5@user/stable"
    def build(self):
        if not self.settings.arch == 'armv8':
            for build_type in ["Debug", "Release"]:
                self.cmake[build_type] = CMake(self, build_type=build_type)
                self.cmake[build_type].definitions["CMAKE_TOOLCHAIN_FILE"] = self.python_requires["helper"].module.setup_toolchain_file()
                self.cmake[build_type].configure(build_folder=self.build_folder + "/" + build_type)
                self.cmake[build_type].build()
    def test(self):
        if not self.settings.arch == 'armv8':
            for build_type in ["Debug", "Release"]:
                self.cmake[build_type].test()
All our test_packages are more or less the same and we never had problems there. Only difference now is that we’re passing the lockfile to the conan create command.
I am really at loss, because I cannot reproduce the error locally. Any conan settings that could influence the behavior? Any ideas / thoughts are highly appreciated!
Issue Analytics
- State:
 - Created 2 years ago
 - Comments:12 (7 by maintainers)
 
Top Results From Across the Web
Strange issues in CI · Issue #864 · wix/Detox
Most likely, Force exiting Jest message has to do with your own tests code. Maybe you forgot to shutdown the mock server or...
Read more >Azure DevOps CI/CD pipeline No package found error
The problem here is that you aren't using a deployment job (or explicitly downloading artifacts from the Build stage) in your Test stage....
Read more >`python setup.py test` fails because of strange working ...
I have an issue while running test in my project. ... The most common source of packaging bugs is when the dependencies change...
Read more >Squeak - Dev - Strange CI error - Smalltalk
I took a pass at writing CI jobs for testing packages in SqueakMap. I used Control simply because it's really small and, well,...
Read more >how to build a GitLab CI testing pipeline in 4 steps
Catch bugs systematically: how to build a GitLab CI testing pipeline in 4 steps · Setting up your UI tests · Step #1:...
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

Hi @KerstinKeller
Conan 1.36 will be released next week, most likely Tuesday or Wednesday, if nothing unexpected happens.
https://github.com/conan-io/conan/pull/8793 merged, this will be released in 1.36