A Committer’s view on Eclipse’s Automatic Error Reporting System
summary
Eclipse Automatic Error Reporting (AERI) ships with Eclipse Mars and collects about 3 million incidents aggregated into roughly 71,000 problems across 160 projects. Committers use a dashboard to drill from problem to incident, inspect stack traces and environment info (product version, OS, Java), mark false positives, link problems to Bugzilla, create a bug, branch, push to Gerrit, rebase, wait for CI and merge; examples include null pointer fixes in the smart import wizard traced to a 2016 commit. Sensitive data is visible only in the committer view.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:34ECLIPSE AUTOMATED ERROR REPORTING
- 3:01FEEDBACK TO USER
- 10:46Low Hanging Fruits
- 10:59EXAMPLES
- 29:59POSSIBLE ENHANCEMENTS
- 32:50CONCLUSION
- 33:59WANT TO USE FOR YOUR OWN PRODUCT?
related talks
23mEclipse Bug's Lifecycle
35mEclipse IDE and RCP Platform: Unveiling the Past, Present and Future
27mMastering your Eclipse IDE - Java Tooling, Tips & Tricks!
45mAutomating away bugs with Error Prone in practice
01h 57mAutomatically improving Java codebases with Error Prone
34mContinuously building impressive software - How can we keep the build green?
48mSay goodbye to bugs and anti-patterns with Error Prone
37mHow to Serve Open Source Maintainers Without Annoying Them?