mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 09:17:43 +03:00
793253ca87
I've witnessed a build ([link], though that will likely expire soon) that failed with a "No space left on device" error after skipping the cleanup step because the machine still had 68GB free. [link]: https://dev.azure.com/digitalasset/daml/_build/results?buildId=87591&view=logs&j=870bb40c-6da0-5bff-67ed-547f10fa97f2&t=deecee86-545a-596e-8b0d-fb7d606fe9f2 With the machines only having 200GB disk size total, cleaning up at 80 is probably going to start hampering the overall efficiency of the cache. It may be time to think about increasing the disk size itself (or finding ways to reduce the size requirements of our builds). Important note, though: we can't actually increase the macOS disk size very much. The failure happened on the `compatibility_linux` job. CHANGELOG_BEGIN CHANGELOG_END |
||
|---|---|---|
| .. | ||
| cron | ||
| da-ghc-lib | ||
| docker | ||
| patch_bazel_windows | ||
| bash-lib.yml | ||
| BUILD | ||
| build-unix.yml | ||
| build-windows.yml | ||
| build.yml | ||
| check-changelog.sh | ||
| clean-up.yml | ||
| clear-shared-segments-macos.yml | ||
| compatibility_ts_libs.yml | ||
| compatibility-windows.yml | ||
| compatibility.yml | ||
| configure-bazel.sh | ||
| copy-unix-release-artifacts.sh | ||
| copy-windows-release-artifacts.sh | ||
| dev-env-install.sh | ||
| dev-env-push.py | ||
| job-variables.yml | ||
| oracle_image | ||
| postgresql.conf | ||
| prs.yml | ||
| publish-artifactory.sh | ||
| publish-platform-independence-dar.yml | ||
| remap-scala-test-short-names.ps1 | ||
| report-end.yml | ||
| report-start.yml | ||
| slack_user_ids | ||
| tell-slack-failed.yml | ||
| upload-bazel-metrics.yml | ||
| windows-diagnostics.ps1 | ||