Skip to content

bisect: always override oldCommit to the merge base commit#633

Merged
meteorcloudy merged 1 commit intomasterfrom
meteorcloudy-patch-5
Nov 22, 2024
Merged

bisect: always override oldCommit to the merge base commit#633
meteorcloudy merged 1 commit intomasterfrom
meteorcloudy-patch-5

Conversation

@meteorcloudy
Copy link
Member

This would resolve branch name like release-8.0.0rc2 to an actual commit hash, which is then a valid Bazel version for Bazelisk.

This avoids error like:

# bazel --bisect=release-8.0.0rc2..e18aad1be363fe40bad2cc67462a6389f381096b test //...


--- Getting the list of commits between release-8.0.0rc2 and e18aad1be363fe40bad2cc67462a6389f381096b

Found 54 commits between (release-8.0.0rc2, e18aad1be363fe40bad2cc67462a6389f381096b]


--- Verifying if the given good Bazel commit (release-8.0.0rc2) is actually good

2024/11/18 12:58:03 could not run Bazel: could not download Bazel: could not resolve the version 'release-8.0.0rc2' to an actual version number: Invalid version 'release-8.0.0rc2'

This would resolve branch name like `release-8.0.0rc2` to an actual commit hash, which is then a valid Bazel version for Bazelisk. 

This avoids error like:
```
# bazel --bisect=release-8.0.0rc2..e18aad1be363fe40bad2cc67462a6389f381096b test //...


--- Getting the list of commits between release-8.0.0rc2 and e18aad1be363fe40bad2cc67462a6389f381096b

Found 54 commits between (release-8.0.0rc2, e18aad1be363fe40bad2cc67462a6389f381096b]


--- Verifying if the given good Bazel commit (release-8.0.0rc2) is actually good

2024/11/18 12:58:03 could not run Bazel: could not download Bazel: could not resolve the version 'release-8.0.0rc2' to an actual version number: Invalid version 'release-8.0.0rc2'
```
@meteorcloudy
Copy link
Member Author

@fweikert ping~

@meteorcloudy meteorcloudy merged commit e812979 into master Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants