How to make use of per-revision artifacts when finding regression?

[jdm]

I’ve identified a regression in rustc that has a wider regression range than I hoped. Bisecting builds locally is challenging for various reasons that aren’t particularly important. It was pointed out to me that there are build artifacts for every revision in that range available on s3, and I can see them via aws s3 ls --no-sign-request s3://rust-lang-ci2/rustc-builds/a722296b6ec17fecd3f16a7d3f9232b83e5de800/. What is the easiest way for me to test these artifacts? Is there rustup integration that I’m overlooking?

[kamalmarhubi]

@jdm I made rust-bisect some time ago. It seems like it might be possible to adapt it to this use case. And that it should be!

[glandium]

There is also cargo-bisect, which, according to https://github.com/rust-lang-nursery/cargo-bisect-rustc/issues/8 being closed, should support this.

[system]

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.