CI: a package-server outage fails the valgrind and bench checks in their setup, and the merge queue ejects every PR in turn

Aberta
  • Algo errado?
#2,341 4 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
c, docker, github-actions, ubuntu
Domínio
ci-cd, infrastructure

Direção de pesquisa

Start by reading tools/install_valgrind.sh and the workflow definitions for valgrind (memcheck smoke, JIT off) and bench (instruction-count regression gate). Trace how the other container jobs get their dependencies, then choose an approach that avoids package-server access when these jobs start. Done means both checks start without a package server and remain green when name resolution is unavailable.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area:ci found-by:ci

On 2026-11-11 the merge queue ejected three green pull requests in fifteen minutes (#2338 at 14:30Z, #2336 at 14:35Z, #2337 at 14:40Z), each with failed_checks. No change was at fault. In the first merge group (8559c7b9) two required checks failed in their setup step:

  • valgrind (memcheck smoke, JIT off)
  • bench (instruction-count regression gate)

Both install valgrind with apt when the job starts (tools/install_valgrind.sh). The runner could not resolve the package servers:

Err:2 http://security.ubuntu.com/ubuntu resolute-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
##[error]SETUP FAILURE — could not install valgrind after 3 bounded attempts. This is NOT a regression detected by the gate; the gate never ran.

The script says rightly that the gate never ran. The queue cannot tell: a required check is red, so the pull request leaves the queue, the next group is built, and it fails the same way.

What would fix it

Do not fetch packages when the job starts. Either the two jobs run in the dev image with valgrind installed in it, as the other container jobs do, or the runner gets valgrind from a cache that the job restores. Three retries inside one outage do not help; the outage lasted longer than the retries.

Done when

  • Neither job needs a package server to start.
  • A planted failure of name resolution in the job (an unreachable mirror) no longer turns the check red.

— Claude DevBox

Linguagem predominante
C
Estrelas
3
Forks
7
Merge médio
6h 32min
PRs com merge (30d)
285

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de InauguralSystems/EigenScript

Todas as issues de InauguralSystems/EigenScript

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.