Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#4,528 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
git, node.js
Domaine
devops, infrastructure

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Jinja
Étoiles
542
Forks
184
Merge moyen
4 j 16 h
PR mergées (30 j)
11

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nodejs/build

Toutes les issues de nodejs/build

Issues similaires

Plus d'issues DevOps

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.