Update JEDI CI action with build cache - #1247
Conversation
|
Is the expectation here that only one set of tests would run, and it would contain 3196 tests? |
|
@shlyaeva - yes this new behavior is expected. We still run unit tests first, then integration tests, but they are reported togeather in the same github "Check Run" object. If unit tests fail, the test finishes early and the GitHub Check Run reports failure for the unit tests. I made this change for two reasons:
|
|
@eap OK, sounds good! One way to speed things up even more would be to run only this repos tests + everything downstream (no need to run anything upstream; for model interface repos this should save quite a bit of time). But this is already altogether much faster, thank you for doing this! |
|
@eap one more question: do we run CI with oasim? |
|
@shlyaeva - yes; here's the configure. Actually, I just added you to the oasim PR since I'm short on reviews.
|
Update to jedi-ci v2 with caching
run-ci-on-draft = true
Issue: JCSDA-internal/jedi-ci#77