a Scientific paper proposal: Is this Build Failure Related to my Patch?, week 2 - #2979
Merged
Conversation
Collaborator
|
Readme is not correctly formatted Got: ['Assignment Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description', 'Relevance'] |
Collaborator
|
Looking forward to the presentation! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Is this Build Failure Related to my Patch? An Empirical Study of Unrelated Build Failures in Continuous Integration
Names and KTH ID
Deadline
Category
Description
This paper was published in Empirical Software Engineering in May 2026.
Continuous Integration systems often execute many builds concurrently, which means that a build failure is not always caused by the code change that triggered the build. Such unrelated build failures can waste developers' time, as they first need to find out whether the problem was actually introduced by their own change.
The paper studies over 70 thousand CI build failures from seven open-source projects. The authors find that developers spend a median of four hours determining whether a failure is related to their code change. They then use issue reports, comments, and commits to build semi-supervised Positive and Unlabeled (PU) learning models for predicting unrelated build failures.
During our presentation, we aim to explain the problem of unrelated CI failures, describe the proposed prediction approach, discuss the main empirical results, and evaluate how such a system could improve the developer feedback loop in CI environments.
Relevance
This paper is highly relevant to DevOps and Week 2 because it focuses directly on Continuous Integration and automated build pipelines. Fast and reliable feedback from CI is a central DevOps practice. Unrelated build failures can slow down development by causing developers to investigate problems that were not introduced by their own changes.
Automatically identifying such failures could reduce unnecessary debugging effort, improve time-to-feedback, and help developers decide what to do.