This appears to have started occurring sometime over the weekend, but is a little hard to narrow down due to being outerloop and not running against main
The last in the chain of successful builds was: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1441125&view=results, which is based on 9aeec7f as the parent commit from main
The first failure was https://dev.azure.com/dnceng-public/public/_build/results?buildId=1441239&view=results, which is based on 32f2c33 as the parent commit from main, other subsequent failures were also on this same commit or later.
The range of potential bad commits is then: 9aeec7f...32f2c33
This leaves:
This appears to have started occurring sometime over the weekend, but is a little hard to narrow down due to being outerloop and not running against
mainThe last in the chain of successful builds was: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1441125&view=results, which is based on 9aeec7f as the parent commit from
mainThe first failure was https://dev.azure.com/dnceng-public/public/_build/results?buildId=1441239&view=results, which is based on 32f2c33 as the parent commit from
main, other subsequent failures were also on this same commit or later.The range of potential bad commits is then: 9aeec7f...32f2c33
This leaves: