Bug Prediction at Google (2011)

harryjo · on July 5, 2015

This was abandoned by Google shortly after launch.

Several previous discussions: https://hn.algolia.com/?query=bug-prediction-at-google.html&...

thrownaway2424 · on July 5, 2015

An unmentioned reason why this didn't work overly well is some people and teams use a "bug-fixing commit" to resolve a feature request, which unfairly marks actively developed code as dangerous. Disorganized teams who didn't track feature developments with bugs didn't get that penalty.

ignoramous · on July 5, 2015

Specifically, read the reply from the author of the blog-post in this thread: https://news.ycombinator.com/item?id=9324418

vmorgulis · on July 5, 2015

I came accross bugspots. It works on git repos and proposes bugfix.

https://github.com/igrigorik/bugspots

amelius · on July 5, 2015

> In fact, as previously noted, 50% of the Google code base changes every month.

Is this because 50% of the code base is new projects? Is Google growing exponentially that fast?

vmorgulis · on July 5, 2015

https://news.ycombinator.com/item?id=3411134

I think it is per file. 50 % of source files (not sure).