LogChunks
Authors:
Open Access
- 29 June 2020
- conference paper
- Published by Association for Computing Machinery (ACM)
- p. 583-587
Abstract
Build logs are textual by-products that a software build process creates, often as part of its Continuous Integration (CI) pipeline. Build logs are a paramount source of information for developers when debugging into and understanding a build failure. Recently, attempts to partly automate this time-consuming, purely manual activity have come up, such as rule- or information-retrieval-based techniques. We believe that having a common data set to compare different build log analysis techniques will advance the research area. It will ultimately increase our understanding of CI build failures. In this paper, we present LogChunks, a collection of 797 annotated Travis CI build logs from 80 GitHub repositories in 29 programming languages. For each build log, LogChunks contains a manually labeled log part (chunk) describing why the build failed. We externally validated the data set with the developers who caused the original build failure. The width and depth of the LogChunks data set are intended to make it the default benchmark for automated build log analysis techniques.Keywords
This publication has 15 references indexed in Scilit:
- A Tale of CI Build Failures: An Open Source and a Financial Organization Perspective2017
- TravisTorrent: Synthesizing Travis CI and GitHub for Full-Stack Research on Continuous Integration2017
- Oops, My Tests Broke the Build: An Explorative Analysis of Travis CI with GitHub2017
- Usage, costs, and benefits of continuous integration in open-source projects2016
- An in-depth study of the promises and perils of mining GitHubEmpirical Software Engineering, 2015
- Quality and productivity outcomes relating to continuous integration in GitHub2015
- Programmers' build errors: a case study (at google)2014
- Modeling continuous integration practice differences in industry software developmentJournal of Systems and Software, 2014
- Improving developer participation rates in surveys2013
- Using benchmarking to advance research: a challenge to software engineering2003