Runner: one tests module after merging step debug and step timeouts#86
Succeededmain33da85cpush by syntaqx · 18m 10s
How this runs on g1t · 26 notes
- check: `actions/checkout` checks out from g1t.
- plan: `actions/checkout` checks out from g1t.
- plan: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
- migrate: `actions/checkout` checks out from g1t.
- migrate: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
- core: `actions/checkout` checks out from g1t.
- core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- core: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
- edge: `actions/checkout` checks out from g1t.
- edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- edge: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
- front: `actions/checkout` checks out from g1t.
- front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- front: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
Set up job0s
No output yet.
Run actions/checkout@v510s
No output yet.
Rust for Workers1s
No output yet.
Cache worker-build1s
No output yet.
Cache worker-build's tools (wasm-bindgen, esbuild)3s
No output yet.
Cache crates3s
No output yet.
Cache the Cargo target9s
No output yet.
Rust for the runner
Skipped.
Cache the runner's build
Skipped.
Install5s
No output yet.
Deploy api1m 18s
No output yet.
Post Cache the Cargo target10s
No output yet.