Skip to content

check if slash already in base

afdaa15
Select commit
Loading
Failed to load commit list.
Merged

Improving the handling of the coefficient path to avoid double slash #264

check if slash already in base
afdaa15
Select commit
Loading
Failed to load commit list.
JCSDA-CI / JEDI integration test: gcc11 failed Nov 19, 2025 in 3h 32m 15s

Failure - 1776 of 1926 tests passing

Details

JEDI integration test: gcc11

Ran 1926 tests. Observed 1776 passing
tests and 150 tests not passing.

Failures

test_MWSurfEM.........................................................................failed
test_ioda_distribution_masterandreplica_mpi_2.........................................failed
test_ioda_distribution_masterandreplica_mpi_3.........................................failed
test_ioda_distribution_masterandreplica_mpi_4.........................................failed
test_ioda_distribution_timewindow.....................................................failed
test_ioda_distribution_build_round_robin_mpi_2_file_set...............................failed
test_ioda_distribution_build_round_robin_mpi_3_file_set...............................failed
test_ioda_distribution_build_round_robin_mpi_4_file_set...............................failed
test_ioda_distribution_masterandreplica_io_pool_mpi_2.................................failed
test_ioda_distribution_masterandreplica_io_pool_mpi_3.................................failed
test_ioda_distribution_masterandreplica_io_pool_mpi_4.................................failed
test_ioda_oops_obsspace...............................................................failed
test_ioda_obsspace....................................................................failed
test_ioda_obsspace_reader_pool........................................................failed
test_ioda_obsspace_out_odc............................................................failed
iodatest_obsspace_out_odc_readbackin..................................................failed
test_ioda_obsspace_out_odc_compare_aircraft...........................................failed
test_ioda_obsspace_out_odc_compare_atms...............................................failed
test_ioda_obsspace_out_odc_compare_gmi................................................failed
test_ioda_obsspace_out_odc_compare_amsua..............................................failed
test_ioda_obsspace_out_odc_compare_groundgps..........................................failed
test_ioda_obsspace_out_odc_compare_sonde..............................................failed
test_ioda_obsspace_out_odc_compare_sonde_mixed........................................failed
test_ioda_obsspace_out_odc_compare_sonde_derived......................................failed
test_ioda_obsspace_out_odc_compare_aod................................................failed
test_ioda_obsspace_out_odc_compare_iasi...............................................failed
test_ioda_obsspace_out_odc_compare_readbackin_aircraft................................failed
test_ioda_obsspace_out_odc_compare_readbackin_atms....................................failed
test_ioda_obsspace_out_odc_compare_readbackin_iasi....................................failed
test_ioda_obsspace_out_odc_compare_readbackin_groundgps...............................failed
Omitting 120 results
test_ioda_bufr_python_parallel........................................................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