Skip to content

Include commit SHA in GitHub API commit query reporting #69

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
chrissimpkins opened this issue Mar 11, 2020 · 1 comment
Closed

Include commit SHA in GitHub API commit query reporting #69

chrissimpkins opened this issue Mar 11, 2020 · 1 comment
Labels
A-reporting Area: Report generation enhancement New feature or request

Comments

@chrissimpkins
Copy link
Member

I ran bisect-rustc with the new GitHub API support (#63) for a rust ICE and landed on a nightly that is outside of the 167 day range for CI / commit bisection support. The report from the tool ended with the commit dump:

commit[0] 2019-08-19UTC: Auto merge of #63579 - alexcrichton:new-lockfile, r=Mark-Simulacrum
commit[1] 2019-08-19UTC: Auto merge of #63715 - Centril:rollup-dga8qtp, r=Centril
commit[2] 2019-08-20UTC: Auto merge of #62727 - SimonSapin:plugins-tls-dylib, r=petrochenkov
commit[3] 2019-08-20UTC: Auto merge of #63497 - eddyb:miri-subst, r=oli-obk
commit[4] 2019-08-20UTC: Auto merge of #63709 - matklad:decomposed-tokens, r=petrochenkov
commit[5] 2019-08-20UTC: Auto merge of #63587 - flip1995:clippyup, r=flip1995
commit[6] 2019-08-20UTC: Auto merge of #63744 - Centril:rollup-g4l3ra9, r=Centril
commit[7] 2019-08-20UTC: Auto merge of #63752 - Centril:rollup-nlxwety, r=Centril

It would be helpful to include the short git commit SHA's in this report so that "manual" bisection can be performed over the commits.

@ehuss ehuss added enhancement New feature or request A-reporting Area: Report generation labels Feb 13, 2024
@ehuss
Copy link
Collaborator

ehuss commented Feb 13, 2024

I'm going to close as the output now says:

found 8 bors merge commits in the specified range
  commit[0] 2022-12-30: Auto merge of #105651 - tgross35:once-cell-inline, r=m-ou-se
  commit[1] 2022-12-30: Auto merge of #105058 - Nilstrieb:no-merge-commits-for-you-only-bors-is-allowed-to-do-that, r=jyn514
  commit[2] 2022-12-31: Auto merge of #106320 - jyn514:revert-merge-check, r=jyn514
  commit[3] 2022-12-31: Auto merge of #106324 - compiler-errors:rollup-2m9njin, r=compiler-errors
  commit[4] 2022-12-31: Auto merge of #106245 - estebank:mutability-suggestions, r=jyn514
  commit[5] 2022-12-31: Auto merge of #106302 - compiler-errors:terr-coerce-w-infer, r=estebank
  commit[6] 2022-12-31: Auto merge of #106275 - Nilstrieb:const-eval-select-me-some-compile-time, r=thomcc
  commit[7] 2022-12-31: Auto merge of #106282 - Ezrashaw:merge-e0465, r=estebank
ERROR: no CI builds available between ce85c98575e3016cf2007d90a85be321e592aa96 and 574b64a97f52162f965bc201e47f0af8279ca65d within last 167 days

I think the commit range there should be sufficient to do a manual bisection. I don't think the sha of each individual commit is necessarily important. However, feel free to reopen if I'm missing something, or if there is more information to include.

@ehuss ehuss closed this as completed Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-reporting Area: Report generation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants