Repository navigation
ctest failure in eckit_test_geo_grid_fesom #303
Description
What happened?
ctest eckit_test_geo_grid_fesom is failing like this for me:
211/246 Test #211: eckit_test_geo_grid_fesom ................................***Failed 0.05 sec
Running 2 tests:
Running case 0: spec ...
Downloading 'https://sites.ecmwf.int/repository/eckit/geo/grid/fesom/pi_N.fesom.ek' to '/home/users/david.davies/cylc-run/DevelopNextBuildBaseLatests/share/make_mo_base__spice_gnu/eckit/tests/geo/eckit_geo_cache/latlon/1/3bb8f659e895bdb7bdd60156ad96879c.ek'...
Download of 0 bytes took 8e-06s.
�[31mTest "spec" failed with unhandled eckit::Exception: Assertion failed: Download: file '/home/users/david.davies/cylc-run/DevelopNextBuildBaseLatests/share/make_mo_base__spice_gnu/eckit/tests/geo/eckit_geo_cache/latlon/1/3bb8f659e895bdb7bdd60156ad96879c.ek' not found @ (/home/users/david.davies/cylc-run/DevelopNextBuildBaseLatests/share/mo-bundle/eckit/src/eckit/geo/cache/Download.cc:182 to_cached_path)�[0m
Stack trace: backtrace [1] stack has 16 addresses
What are the steps to reproduce the bug?
Build and run ctests.
I am using ENABLE_CURL=OFF if that is relevant.
Version
develop
Platform (OS and architecture)
Linux
Relevant log output
Accompanying data
No response
Organisation
Met Office
Activity
wdeconinck commentedon Jul 7, 2026
Probably that requires ENABLE_CURL=ON, is there another fallback mechanism @pmaciel ?
pmaciel commentedon Jul 7, 2026
Well, this is an error: the tests are designed not to use curl, with the required (small) file should be found in the checkout repository sources. I'm trying to design the tests so curl isn't needed, and there's a small number of files bundled in to test for this purpose
However, I've made an error in the logic somewhere, as the test (erroneously) cannot find the file, and tries to download it using curl. I'll have a look
pmaciel commentedon Jul 7, 2026
I've added cache versioning in a previous commit, and the tests supporting files didn't accompany this change. I've moved the testing files to the expected location.
@DJDavies2 can you confirm with your testing? Thanks
DJDavies2 commentedon Jul 8, 2026
Thanks, I have checked the update, it seems to work for me now.