Rich Drewes, regarding bug 1094800, both the specific commit causing the regression, and whether that commit is the same one that caused your regression is unknown. As well, you both have different hardware. Hence, waiting for the final bisect results from it would delay your issue being addressed.
if you can bisect the issue down to a specific commit, this would maximize the speed for your problem to be addressed.
Rich Drewes, regarding bug 1094800, both the specific commit causing the regression, and whether that commit is the same one that caused your regression is unknown. As well, you both have different hardware. Hence, waiting for the final bisect results from it would delay your issue being addressed.
if you can bisect the issue down to a specific commit, this would maximize the speed for your problem to be addressed.