Labelled corpus of 90 days of ci.yml failures, as evidence for #2177
Mantenedores costumam responder em até 2 dias
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Funcionalidade
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- github, github-actions, rust
- Domínio
- ci-cd, data-engineering, observability
Direção de pesquisa
Read the linked corpus repository, especially tool/harvest.sh, tool/classify.py, tool/label.py, and tool/labels.yaml, then review #2177 and #2523 for project context. The issue asks whether to build a project hosted dashboard that refreshes the analysis; confirm the project's interest and agree on scope before implementation. Done means an accepted proposal defining where it runs, what it displays, and how the scheduled refresh works.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
For the flake tracking in #2177 I wanted to know how much of the CI failure volume is flaky, and from which causes. So I classified every failed ci.yml job from 13 August to 10 November 2026: 2638 failed jobs across 890 runs, grouped by log signature and labelled flake, real or unclear.
The corpus, the per-job labels and the scripts are here: https://github.com/andrewdunndev/bootc-ci-corpus
824 of those jobs are the two required-checks gates, which mirror failures in other jobs. The other 1814 split like this:
| Label | Jobs | Share | Largest causes (jobs) |
|---|---|---|---|
| real | 1206 | 66% | grub2-efi-cc absent from the ELN repos (282); PR-specific test failures (225); one PR's VM launch failures (176) |
| flake | 530 | 29% | quay blob EOF and 502/504 (134); dnf mirror 404 or timeout (82); guest reboot lost in tmt plans (66); runner lost (32) |
| unclear | 78 | 4% | not enough in the log to say |
- Labels are rule-assigned. The rules are in
tool/labels.yaml: a default label per signature, sub-cause rules that match the log tail, and one override. A non-gate job whose same sha passed on another attempt is labelled flake (261 of the 530 flakes). - The grub-cc window and that one PR inflate the real share. Without them, real is 55% of 1356 jobs.
- A libvirt session socket failure at VM launch is still occurring (5 jobs from 1 to 10 November, 24 in all) and isn't in #2177. Neither are the quay blob EOF failures (#2177 has the 502 case).
What it's for
Evidence for #2177: which flakes cost the most jobs, which are fixed, and which still occur. labels.jsonl also works as an answer key for the ci-triage analyzer, and for the post-merge triage in #2523.
How it was labelled
AI agents wrote the rules from an earlier hand-labelled pass. Every label comes from labels.yaml, and the reason field in labels.jsonl says what set it: the signature default, a log-tail or PR rule, or the same-sha override. Two hand sub-causes have no rule and stay at signature level; corpus.md lists them.
Rerun or extend
tool/harvest.sh . raw work # needs gh, jq, python3; GET requests only
python3 -I tool/classify.py jobs.jsonl tool/signatures.yaml assignments.jsonl
python3 -I tool/label.py jobs.jsonl assignments.jsonl tool/labels.yaml labels.jsonl corpus.csv corpus.md
Same inputs give byte-identical outputs. The harvest keeps the last 150 lines of each job log; those tails are not in the repository.
Comments wanted
- Rules that look wrong, most likely in
vm-launch-failedandtmt-plans-failed-uncategorised, where one signature holds both flake and real jobs. - Whether the libvirt socket and quay blob EOF failures belong in #2177.
- Whether per-job signatures are the right key for scoring ci-triage.
- Known gaps: cancelled jobs (141) aren't harvested.
@cgwalters, would this kind of analysis be a welcome contribution as part of the project itself, on a dashboard that updates on its own? The harvest and labels already rerun from scratch, so a scheduled job could keep the numbers behind #2177 current. I'd be glad to build it if so, or keep it outside the project if you'd rather.
- Linguagem predominante
- Rust
- Estrelas
- 2.3k
- Forks
- 230
- Merge médio
- 2d 11h
- PRs com merge (30d)
- 42
Preparar o ambiente
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de bootc-dev/bootc
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
Mantenedores costumam responder em até 2 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
Mantenedores costumam responder em até 2 dias
-
install: improve error message when systemd-boot is selected without composefs backendTalvez livre de novo Um pull request para esta issue foi fechado sem ser mesclado. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
Mantenedores costumam responder em até 2 dias
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 55/100
Mantenedores costumam responder em até 2 dias
-
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 30/100
Mantenedores costumam responder em até 2 dias
Todas as issues de bootc-dev/bootc
Issues semelhantes
-
llm translation
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 85/100
Mantenedores costumam responder em até 1 dia
-
documentation good first issue trivial
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 84/100
Mantenedores costumam responder em até 1 dia
-
[Bug]: layer.move to the place a layer already has fails and stops a script; with several layers it leaves an empty undo stepTalvez já em andamento @jgregoriorincon assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
opengeos/RustGIS#2621 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
good first issue web
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 92/100
Mantenedores costumam responder em até 1 dia