Use VADER for insitu/potential TL/AD #964
Open
JCSDA-CI / JEDI unit test: gcc
succeeded
Dec 30, 2025 in 1h 3m 9s
ran 72 tests
Details
JEDI unit test: gcc
Ran 72 tests. Observed 72 passing
tests and 0 tests not passing.
- CDash results for test
- Test logs
- CI Job (requires AWS login)
- CI Job logs (requires AWS login)
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