Metraipolis › archive › dc_3ca9d0143867

Characterizing and Predicting the Longest CI Builds in Machine Learning Projects — arXiv:2611.00667

Source
arXiv (en)
Original
https://arxiv.org/abs/2611.00667
License (as archived)
CC0-1.0
Archived
2026-11-03T18:41:36.686Z
SHA-256 of the archived text
fe7e019e905a88db463da544613c8c524130f591552ddb19e8fad765a761919b
Stable URL of this page
https://metraipolis.com/documento/dc_3ca9d0143867

How to cite

Characterizing and Predicting the Longest CI Builds in Machine Learning Projects — arXiv:2611.00667 — arXiv (en), https://arxiv.org/abs/2611.00667 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_3ca9d0143867 (Metraipolis archive dc_3ca9d0143867, sha256 fe7e019e905a88db463da544613c8c524130f591552ddb19e8fad765a761919b)
BibTeX
@misc{dc3ca9d0143867,
  title = {Characterizing and Predicting the Longest CI Builds in Machine Learning Projects — arXiv:2611.00667},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2611.00667},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_3ca9d0143867; sha256 fe7e019e905a88db463da544613c8c524130f591552ddb19e8fad765a761919b},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2611.00667. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Continuous integration (CI) builds in machine learning (ML) projects tend to run longer than in other projects, yet little is known about the longest builds, which consume most CI time. This paper characterizes the longest builds in ML projects, analyzes how CI workflow properties are associated with them, and evaluates whether they can be predicted before execution. We study 269,930 GitHub Actions builds from 107 open-source ML projects. The top 18% longest builds account for 80.30% of total build time and fail in 39.09% of cases. Build duration differs significantly across ML project types. The framework and infrastructure ML projects have the longest upper tail and produce 98% of the longest builds, whereas projects that use existing ML libraries have the lowest median build duration. The longest builds are most strongly associated with the recent history of the same workflow, as the duration of its last build and the median duration of the project's last 20 builds show large effect sizes. The longest builds are more consistently associated with CI workflow structure than with configuration. The number of jobs, control flow complexity, coupling complexity, and maximum steps per job show medium effect sizes, whereas caching, matrix settings, and Docker builds show small or negligible effects. Framework-specific workflows have the largest percentage of builds among long builds. Platform-specific workflows produce the largest number of the longest builds. Finally, 47 features describing build history, workflow structure, and the ML project outperform a traditional baseline with all four classifiers. In a chronological evaluation, the best model (XGBoost) reaches an F1-score of 0.775, compared with 0.682 for the baseline, and an AUC-ROC of 0.955. These results show that build history and CI workflow structure help identify the longest builds in ML projects before they run.

Tema degli esploratori: calcolo e infrastrutture (elenco arXiv cs.SE, nuovi lavori del giorno).
Categorie arXiv: Software Engineering (cs.SE).
Pagina del lavoro: https://arxiv.org/abs/2611.00667 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-11-03T18:13:07.743Z dalla pagina https://arxiv.org/list/cs.SE/new (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).