The GitHub Actions job "Fory CI" on fory.git/main has failed.
Run started by GitHub user chaokunyang (triggered by chaokunyang).

Head commit for run:
243755e3abcfefeda4cce7d00c99c0830f36552d / Charlie_Moon 
<[email protected]>
perf(ci): add Cargo caching to Rust CI jobs (#3431)

## Why?

The Rust CI currently takes approximately 3-5 minutes to complete. By
adding Cargo dependency caching, we can reduce build times by caching
compiled dependencies between runs.

## What does this PR do?

- Adds `Swatinem/rust-cache@v2` to the `rust` job in
`.github/workflows/ci.yml`
- Adds `Swatinem/rust-cache@v2` to the `rust_xlang` job in
`.github/workflows/ci.yml`
- Configures cache to use the `rust` workspace directory

## Related issues

Closes #2889

## Does this PR introduce any user-facing change?

No user-facing changes. This only affects CI execution time.

- [ ] Does this PR introduce any public API change?
- [ ] Does this PR introduce any binary protocol compatibility change?

## Benchmark

**CI execution time comparison:**

| Job | Before (main) | After (with cache) | Improvement |
|-----|---------------|-------------------|-------------|
| Rust CI (ubuntu-latest) | 3m 13s | 2m 54s | ✅ **-19s** |
| Rust CI (macos-14) | 3m 02s | 2m 53s | ✅ **-9s** |
| Rust CI (macos-latest) | 3m 16s | 3m 22s | ⚠️ +6s |

**Cache details:**
- Cache size: ~14MB
- Cache includes: `~/.cargo/bin`, `~/.cargo/registry`, `~/.cargo/git`,
`rust/target`
- Logs confirm: `Cache restored successfully` with full match
- Cache key format: `v0-rust-rust-Linux-x64-<env-hash>-<lockfile-hash>`

**Notes:**
- Ubuntu shows consistent improvement (~19s faster)
- macOS results are within normal variance range for GitHub Actions
runners
- Cache prevents re-downloading and re-compiling Rust dependencies on
subsequent runs

Report URL: https://github.com/apache/fory/actions/runs/22719205837

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to