mirror of
https://github.com/obi1kenobi/cargo-semver-checks-action.git
synced 2024-11-24 00:49:34 +01:00
300d7d49b9
It's always caching. Or DNS. This time it was caching. A while back, we changed the default cache key prefix from empty-string to `semver` so that our cache key names don't start with a dash, since users found that confusing. We should have updated these tests accordingly at the time, but we did not. So how did the PR with the change pass? It used the caches from older runs of the same job which used the old names. When those caches expired and were GC'd by GitHub, the jobs started failing. This is what broke CI for #77. This PR will fix it. |
||
|---|---|---|
| .. | ||
| setup-test-workspace | ||
| ci.yml | ||
| README.md | ||
| test-action.yml | ||
| test-build.yml | ||
| test-cache.yml | ||
| test-inputs.yml | ||
The testing workflow is divided into several parts:
test-action.yml, which contains simple, general integration tests of the action that should be run on each platform
and the following ones run on ubuntu-latest:
test-build.ymlcontaining source-related checks: linters, formatters and verifying whether the sources matchdist/directory,test-inputs.ymlcontaining specific integration tests checking whether the action inputs are processed properly,test-cache.ymlfocusing on veryfing whether the baseline rustdoc is cached correctly.
setup-test-workspace is a helper action that creates a workspace containing two crates: the test fork of ref_slice and a dummy crate that has no matching baseline version on crates.io.