Use VADER for insitu/potential TL/AD #964
Open
JCSDA-CI / JEDI integration test: gcc
succeeded
Dec 30, 2025 in 2h 35m 30s
Success with some failures; 2981 of 3044 tests passing
Details
JEDI integration test: gcc
Ran 3044 tests. Observed 2981 passing
tests and 63 tests not passing.
- CDash results for test
- Test logs
- CI Job (requires AWS login)
- CI Job logs (requires AWS login)
Failures
test_vader_recipe_SeaWaterPotentialTemperature_A......................................failed
test_vader_recipe_SeaWaterTemperature_A...............................................failed
test_vader_recipe_SeaWaterTemperature_B...............................................failed
test_mpasjedi_geometry................................................................failed
test_mpasjedi_state...................................................................failed
test_mpasjedi_model...................................................................failed
test_mpasjedi_increment...............................................................failed
test_mpasjedi_errorcovariance.........................................................failed
test_mpasjedi_linvarcha...............................................................failed
test_mpasjedi_geometry_iterator_2d_2pe................................................failed
test_mpasjedi_geometry_iterator_3d_2pe................................................failed
test_mpasjedi_getvalues...............................................................failed
test_mpasjedi_obslocalization.........................................................failed
test_mpasjedi_obslocalization_vertical................................................failed
test_mpasjedi_obslocalizations........................................................failed
test_mpasjedi_forecast................................................................failed
test_mpasjedi_hofx3d..................................................................failed
test_mpasjedi_hofx3d_nbam.............................................................failed
test_mpasjedi_hofx4d..................................................................failed
test_mpasjedi_hofx4d_pseudo...........................................................failed
test_mpasjedi_convertstate............................................................failed
test_mpasjedi_converttostructuredgrid_latlon..........................................failed
test_mpasjedi_parameters_bumpcov......................................................failed
test_mpasjedi_parameters_bumploc......................................................failed
test_mpasjedi_parameters_diffusion....................................................failed
test_mpasjedi_gen_ens_pert_B..........................................................failed
test_mpasjedi_dirac_bumpcov...........................................................failed
test_mpasjedi_dirac_bumploc...........................................................failed
test_mpasjedi_dirac_diffusion_duplicated..............................................failed
test_mpasjedi_dirac_diffusion_univariate..............................................failed
Omitting 33 results
test_mpasjedi_3dhybrid_bumpcov_bumploc_2pe............................................failed
CI System Information
A full explanation of all features, behaviors, and configuration options
can be found in the JEDI Infra knowledge base article on CI.
Re-run tests
Re-run tests by opening the GitHub check "start-jedi-ci / launch-tests"
and clicking the "Re-run all jobs" button on the right.
- Pending, incomplete, or hanging tests will be cancelled and re-run.
- Compute resources for prior tests will be released.
Annotations Quick reference
Presubmit tests can be controlled by single-line annotations in the pull
request description. These annotations will be re-examined for each run.
Each configuration setting must be on a single line, but order and
position does not matter.
Here is an example of their use:
# Build tests with other unsubmitted packages.
build-group=https://github.com/JCSDA-internal/oops/pull/2284
build-group=https://github.com/JCSDA-internal/saber/pull/651
# Enable tests for your draft PR (disabled by default).
run-ci-on-draft=true
# Use a specific compiler instead of selecting one at random.
# Must be "gcc", "gcc11", or "intel"
jedi-ci-test-select=gcc
# Select the jedi-bundle branch used for building. Using this option
# disables the build cache.
jedi-ci-bundle-branch=feature/my-bundle-change
Loading