Closed matthiaskrgr closed 1 year ago
I think that is normal. The unrolled perf builds are force-pushed to the try-perf
branch. The commits will eventually get gc'd, and thus not preserved. You'll need to look at the rollup PR to determine which PR the unrolled commit corresponds to. Since cargo-bisect-rustc is parsing the comment with the PR list, it could probably retain the unrolled PR # and print that in additional to the commit hash.
cc @apiraino
code, saved as
treereduce.out
from https://github.com/rust-lang/rust/issues/116303bisected via
script.sh
which containedand `
what is interesting is that
9a0b251595db987bcdb12442cb756a800f798468
does not exist in my personal clone of the rustc repo, and https://github.com/rust-lang-ci/rust/commit/9a0b251595db987bcdb12442cb756a800f798468 404s :|