unit test compilation error

[Byron Blay (bblay-mo)]

Hi, I'm quite stuck trying to add a new unit test.

To include the test target, I uncomment this line but I get the following error:

18:55:06 Analysing kernel/aviation_icao_heights_kernel_mod_test.F90
18:55:07 Building dependencies.mk
Traceback (most recent call last):
  File ".../lfric_apps/interfaces/physics_schemes_interface/working/scratch/lfric_core/infrastructure/build/tools/dependerator/database.py", line 544, in get_compile_dependencies
    prerequisite_file, prerequisite_type = unit_cache.details(
                                           ^^^^^^^^^^^^^^^^^^^
  File ".../git/lfric_apps/interfaces/physics_schemes_interface/working/scratch/lfric_core/infrastructure/build/tools/dependerator/database.py", line 599, in details
    raise DatabaseException(f"Unable to find unit '{unit}'")
dependerator.database.DatabaseException: ("Unable to find unit 'extrusion_config_mod'", None)

The test target includes planet_constants_mod, which then tries to include this extrusion_config_mod, which doesn't exist. I suspect it's created by the configurator.

You may also notice a commented-out, clutching-at-straws attempt at using feign_config_mod. This didn't work either.

Many thanks for any advice!

[Ricky Wong (mo-rickywong)]

Hi Byron,
You're correct in that, when setting up the unit-test all the required configuration namelist variables accessed via use statements in the code called will need to be set. This is done via feigners to get the right values to the right modules. However, the rose-meta.conf file determines the *config_mod files built by the configurator. For physics_interfaces, there is no rose-meta.conf file in place. So the error message is correct, there is no file as there is no rose-meta.conf file

However, kernels should not be dependent on global module scope variables and work is active in remove all module scope access to variables from kernels. All namelist dependent variables fall into this category and should be passed in via argument list, i.e. the value of g_over_r

See Steps to remove module scope access from kernels in. MetOffice/lfric_apps#357

Ricky

[Byron Blay (bblay-mo)]

Thanks Ricky, that fixed it.

In case it's of interest, I also couldn't access planet_constants from a unit test, so I hard-coded it.