3 ms·
The core assumptions of the algorithm: - if a file introduced introduced a bug recently, it will tend to introduce bugs again - new files added with the bug in
by aavshr 6y ago
The core assumptions of the algorithm:
- if a file introduced introduced a bug recently, it will tend to introduce bugs again
- new files added with the bug introducing file will tend to introduce bugs
- other files changed with the bug introducing file will tend to introduce bugs
- files often changed together with the bug introducing file will tend to introduce bugs soon
fixCache maintains a fixed-size cache of these bug-prone files based on bug fix-commits. This helps in prioritizing verification and testing resources (right now it only updates a pull request with a comment and a label). If a file no longer introduces a bug, it will eventually be replaced from the cache.
- remram 6y agoAre you sure it's not discovering bad developers? Maybe critical areas, e.g. that have the same amount of bugs as the rest but are complained about more? (since the algorithm can only consider bugs that have been reported, so biased to areas important to users) Or maybe that are prioritized by management? (since it considers fixed bugs, so bias towards bugs that were fixed first) Hopefully an increased scrutiny on new patches to those areas leads to fewer bugs getting in which breaks the feedback loop, but if bugs are fixed in separate commit this sounds like it could have negative effects (specific developers/areas getting all the attention, leading to the discovery of more bugs/nitpicks there, reinforcing the bias...).