Fix CI failures when commits are added fast
Fix CI failures when commits are added fast

With a fetch depth of 1 azure pipelines will always clone the master branch
with only the top most commit and then try to check out the commit that
is to be tested. This fails when commits are added quickly, because then
test jobs that weren't fast enough to start will check clone only the newly
added commit and then checking out the commit to test fails because that's
not part of the cloned repository.

softmoth/rakudo,nbrown/rakudo,tbrowder/rakudo,tbrowder/rakudo,labster/rakudo,MasterDuke17/rakudo,labster/rakudo,rakudo/rakudo,rakudo/rakudo,MasterDuke17/rakudo,salortiz/rakudo,MasterDuke17/rakudo,MasterDuke17/rakudo,salortiz/rakudo,nbrown/rakudo,tbrowder/rakudo,tbrowder/rakudo,tony-o/rakudo,labster/rakudo,MasterDuke17/rakudo,salortiz/rakudo,nbrown/rakudo,MasterDuke17/rakudo,softmoth/rakudo,labster/rakudo,nbrown/rakudo,nbrown/rakudo,softmoth/rakudo,tbrowder/rakudo,tony-o/rakudo,softmoth/rakudo,tony-o/rakudo,rakudo/rakudo,labster/rakudo,salortiz/rakudo,tony-o/rakudo,rakudo/rakudo,tbrowder/rakudo,salortiz/rakudo,rakudo/rakudo,labster/rakudo,tony-o/rakudo,rakudo/rakudo,nbrown/rakudo,tony-o/rakudo,salortiz/rakudo,softmoth/rakudo