bootstrap: don't use --merges to look for commit hashes for downloading artifacts
          #89655
        
          
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Shallow clones (and possibly worktrees, though I can't seem to reproduce the problem there) can cause
git rev-list --mergesto falsely return no results, even if a merge commit is present. Stop using the--mergesoption when looking for commit hashes that have build artifacts.--first-parentand[email protected]should be sufficient.Also exit with an error if the configuration asks for artifacts to be downloaded and we can't determine an appropriate commit hash to use to download artifacts.
Fixes #87890.
r? @jyn514
@rustbot label +A-rustbuild +A-contributor-roadblock