Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

`binary_tmp` directory on test-mnx-ubuntu2204-x64-1 causing space issues and PR test failures

Offen
  • Stimmt etwas nicht?
#4,528 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 3 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
git, node.js
Bereich
devops, infrastructure

Rechercherichtung

Start by checking how the binary_tmp repository is created, updated, and cleaned up on the workspace machine, then compare its current size with the earlier 80GB figure. Identify cleanup or retention options that reduce repository growth without breaking PR tests or git_rebase jobs. Done means a practical way to control the repository size is identified and the workspace queues remain healthy.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

incident

Today the subject workspace machine hit an out of disk space condition causing PR tests to fail if they were scheduled on that machine and also causing all git_rebase jobs to fail as the binary_tmp repository they use is hosted on this workspace machine.

Previously I'd see the repository run at about 80GB but today it is sitting at just over 125GB in size. This seemingly unbounded increase should be considered unsustainable.

The rest of the iojs workspaces on the machine are now totalling about 270GB which is broadly consistent with the other two workspace machines. I expect that this figure has also increased as the size of the repository has increased over time although we have also places restrictions ont he number of parallel jobs that node-test-commit can run which will have partially mitigated the larger sizes, although it would seem not be enough.

This issue should cover identifying any means by which we can reduce/clean up the size of the binary_tmp repository.

At the time of writing I've cleared up a small amount of space (30GB) but will leave that workspace machine online so it can be dedicated for the binary_tmp repository for now pending a resolution. We should keep an eye on the queues to make sure nothing is blocked/deadlocked by only having two workspace systems available.

Vorherrschende Sprache
Jinja
Sterne
542
Forks
184
Ø Merge
4 T. 16 Std.
Gemergte PRs (30 T.)
11

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nodejs/build

Alle Issues in nodejs/build

Ähnliche Issues

Weitere Issues zu DevOps

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.