diff options
| author | bors-servo <infra@servo.org> | 2023-06-09 20:08:47 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-06-09 20:08:47 +0200 |
| commit | edd197c74e7edb0b83cec11f23e45d7042162666 (patch) | |
| tree | 8d142d3faeff67d63a30e6f7bf51a56024c2b8cc /components/script | |
| parent | f63f981654453c0687922f6748f4bf20fac7e66e (diff) | |
| parent | b3e4413f4e8eaf767044289b84f60e389199c678 (diff) | |
| download | servo-edd197c74e7edb0b83cec11f23e45d7042162666.tar.gz servo-edd197c74e7edb0b83cec11f23e45d7042162666.zip | |
Auto merge of #29865 - sagudev:win-target, r=mrobinson
windows workflow use C drive as target directory
Currently we clone to drive D (default drive in GitHub Actions), then copy to drive C, then build from there (due to low disk space on D drive). In this PR instead of copying to C drive we only set `CARGO_TARGET_DIR` to C drive, the build is reading source files from D and writing target files to C drive. This gets us approx. -20min.
Try-windows build available [here](https://github.com/sagudev/servo/actions/runs/5219706997/jobs/9421863750).
What do we lose? Well copying step was good benchmarker for GitHub runner machines, fast windows machines spend ~5min in copying step while slow machines ~8min.
For the future: I do believe that D drive may be faster for writing, so switching roles could benefit us, but it will require slow (like copying step) clone.
Diffstat (limited to 'components/script')
0 files changed, 0 insertions, 0 deletions