digitalmars.D - Regressions and git bisect - an app for that?
- Walter Bright (4/4) Feb 13 2020 Speaking of git bisect, a lot of great work has been put into automating...
- mate (4/10) Feb 13 2020 I think that digger, by Vladimir, does that:
- John Colvin (2/13) Feb 13 2020 Yup, digger is great. It's saved me a lot of time.
- Walter Bright (3/16) Feb 13 2020 Anyone want to apply that to the regression list?
- Mathias Lang (7/13) Feb 14 2020 Vladimir gave a presentation about it at DConf:
Speaking of git bisect, a lot of great work has been put into automating things with the test suite, and extra things like generating test profile coverage. It could be an ongoing nice timesaver if a tool could be added to git that, for regressions, automatically figured out which PR caused the breakage.
Feb 13 2020
On Thursday, 13 February 2020 at 09:26:14 UTC, Walter Bright wrote:Speaking of git bisect, a lot of great work has been put into automating things with the test suite, and extra things like generating test profile coverage. It could be an ongoing nice timesaver if a tool could be added to git that, for regressions, automatically figured out which PR caused the breakage.I think that digger, by Vladimir, does that: https://github.com/CyberShadow/Digger
Feb 13 2020
On Thursday, 13 February 2020 at 09:40:46 UTC, mate wrote:On Thursday, 13 February 2020 at 09:26:14 UTC, Walter Bright wrote:Yup, digger is great. It's saved me a lot of time.Speaking of git bisect, a lot of great work has been put into automating things with the test suite, and extra things like generating test profile coverage. It could be an ongoing nice timesaver if a tool could be added to git that, for regressions, automatically figured out which PR caused the breakage.I think that digger, by Vladimir, does that: https://github.com/CyberShadow/Digger
Feb 13 2020
On 2/13/2020 3:53 AM, John Colvin wrote:On Thursday, 13 February 2020 at 09:40:46 UTC, mate wrote:Anyone want to apply that to the regression list? https://issues.dlang.org/buglist.cgi?bug_severity=regression&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=230123&query_format=advancedOn Thursday, 13 February 2020 at 09:26:14 UTC, Walter Bright wrote:Yup, digger is great. It's saved me a lot of time.Speaking of git bisect, a lot of great work has been put into automating things with the test suite, and extra things like generating test profile coverage. It could be an ongoing nice timesaver if a tool could be added to git that, for regressions, automatically figured out which PR caused the breakage.I think that digger, by Vladimir, does that: https://github.com/CyberShadow/Digger
Feb 13 2020
On Thursday, 13 February 2020 at 09:26:14 UTC, Walter Bright wrote:Speaking of git bisect, a lot of great work has been put into automating things with the test suite, and extra things like generating test profile coverage. It could be an ongoing nice timesaver if a tool could be added to git that, for regressions, automatically figured out which PR caused the breakage.Vladimir gave a presentation about it at DConf: https://www.youtube.com/watch?v=1viQK8w6370 I highly recommend watching the whole video but in case you're in a hurry, the Digger part starts here: https://youtu.be/1viQK8w6370?t=1850
Feb 14 2020