On Thu, Jan 30, 2025 at 08:32:28AM +0000, Heinrich Schuchardt wrote: > On 1/30/25 08:08, Heinrich Schuchardt wrote: > > Hello Simon, > > > > when running 'make tests' locally I get: > > > > test/py/tests/test_dm.py . > > > > ============================================================================== > > short test summary info > > =============================================================================== > > SKIPPED [2] test/py/conftest.py:625: .config feature "sandbox" enabled > > SKIPPED [1] test/py/tests/test_bootstage.py:39: No bootstage environment > > file is defined > > SKIPPED [1] test/py/tests/test_cat/test_cat.py:8: Setup failed > > SKIPPED [1] test/py/tests/test_dfu.py:114: got empty parameter set > > ['env__usb_dev_port'], function test_dfu at /test/py/tests/test_dfu.py:113 > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! _pytest.outcomes.Exit: Lab failure: > > Timeout executing 'dm drivers > > ': Marking connection bad - no other tests will run > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > > > > > Shouldn't the required boardenv_* files be generated by running 'make > > tests'? > > > > Best regards > > > > Heinrich > > When installing all packages mentioned in tools/docker/Dockerfile the DM > tests are executed. > > What is missing is an error message which package or tool is needed when > the boardenv_* files cannot be generated.
The boardenv_ files are not generated, they're configuration files. sandbox does not use one today (but perhaps a few more tests would run if there was one) and at least for CI we use https://source.denx.de/u-boot/u-boot-test-hooks -- Tom
signature.asc
Description: PGP signature
