https://issues.dlang.org/buglist.cgi?bug_severity=regression&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=230104&query_format=advanced

Could use help in the form of using git bisect to determine which PR produced the regression. This can help isolate the reasons much faster!

On Thursday, 13 February 2020 at 09:20:09 UTC, Walter Bright wrote:
> https://issues.dlang.org/buglist.cgi?bug_severity=regression&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=230104&query_format=advanced
>
> Could use help in the form of using git bisect to determine which PR produced the regression. This can help isolate the reasons much faster!

What regression bug is the easiest one to start working on for newbies like me?

On 2/13/2020 8:15 PM, 12345swordy wrote:
> On Thursday, 13 February 2020 at 09:20:09 UTC, Walter Bright wrote:
>> https://issues.dlang.org/buglist.cgi?bug_severity=regression&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=230104&query_format=advanced 
>>
>>
>> Could use help in the form of using git bisect to determine which PR produced the regression. This can help isolate the reasons much faster!
> 
> What regression bug is the easiest one to start working on for newbies like me?

Many have the offending PR already identified, so skip those. The others will often say "worked in DMD x.xx and fails with DMD y.yy" where x.xx < y.yy.

The idea is then to use digger to determine which change caused the failure:

  https://github.com/CyberShadow/Digger

Just pick any where success/failure is pretty clear and the failing example is clear.

Even doing just one will be useful.

Thanks!

On Friday, 14 February 2020 at 04:15:42 UTC, 12345swordy wrote:
> On Thursday, 13 February 2020 at 09:20:09 UTC, Walter Bright wrote:
>> https://issues.dlang.org/buglist.cgi?bug_severity=regression&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=230104&query_format=advanced
>>
>> Could use help in the form of using git bisect to determine which PR produced the regression. This can help isolate the reasons much faster!
>
> What regression bug is the easiest one to start working on for newbies like me?

If you were referring to actually fixing the regression and not discover the offending PR, then I suggest that you pick one that pinpoints the PR that caused it and try to understand what changes led to it. Once you do that, in most cases, the fix should be straightfoward, by adding a check for the missing bits.

On 2/13/20 4:20 AM, Walter Bright wrote:
> https://issues.dlang.org/buglist.cgi?bug_severity=regression&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=230104&query_format=advanced 
> 
> 
> Could use help in the form of using git bisect to determine which PR produced the regression. This can help isolate the reasons much faster!

Thanks Walter

20484 	is mine

https://issues.dlang.org/show_bug.cgi?id=20484

I already did the work and found the commit. It is in the initial bug report.

Also of note the change inducing the commit was not in the changelog, but should have been.