Restore required free space on the hosted CI runner

Open
  • Is something wrong?
#389 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

All three current checks on PR #378 stop in OVH build resources before Rust or generated-code execution. The retained logs show 6.8 GiB available on the 72 GiB runner filesystem; existing guards require 16 GiB for the main suite and 8 GiB for generated suites.

Scope

Restore runner capacity using a read-only storage and active-job audit first. Identify only provably disposable Ferrule-generated artifacts and retain required failure/verification evidence before any eligible retirement. Own the runner-capacity report and any focused capacity-policy correction; keep this separate from PDF implementation.

Dependencies and ownership

Coordinate with #359/#360 for per-job ownership, closure and archive retirement. Their safe-retirement gates remain in force. Do not concurrently mutate shared CI build caches or change provider allocation without a concrete reviewed plan.

Acceptance

  • Retain the original failed logs and actual runner disk/cache/active-job inventory.
  • Identify artifact ownership, live users and required evidence for any proposed reclaimable paths.
  • Qualify complete retention and closed ownership before retiring eligible generated artifacts; obtain approval for uncertain ownership or necessity.
  • Restore the existing 16/8 GiB floors with measured headroom; do not lower them to make checks start.
  • Rerun the affected main/generated jobs and keep capacity admission distinct from their test outcomes.
  • Record the result and remaining constraints in the coordinated issue map.

Exclusions

No PDF behavior, fixture/oracle, Rust warning, test expectation or worker-limit changes. No speculative deletion of user files, active caches or retained failure evidence.

I am auditing the observed capacity failure. Original failures: main job, generated crates, generated mappings.

Mitigation: OVH_RUNNER_ENABLED=false routes newly scheduled native/generated checks to GitHub-hosted runners. The original variable, failed job/run/head/attempt identities and workflow bodies remain retained. The three retried PR #390 jobs passed the original capacity admission boundary; main lint then failed on inherited ownership-test helper gates, tracked by #392. This does not qualify OVH capacity repair or archive retirement.

The OVH files/service remain intact. No cleanup, service change or resource-floor reduction occurred; original failures and the read-only inventory remain retained.

Dominant language
Rust
Stars
1
Forks
0
Avg merge
2h 50m
Merged PRs (30d)
571

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DeandreT/ferrule

All issues in DeandreT/ferrule

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.