Bug 1760743 Comment 11 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Mike Hommey [:glandium] from comment #10)
> You can try https://github.com/rust-lang/cargo-bisect-rustc to bisect further.

Thanks. Using that tool to populate my available toolchains (and then selected the current toolchain as the default, and built Firefox, clobbering my objdir and sccache-dir each time).

From testing those builds, it actually seems that the artifact for commit acbe4443c is in fact "good" (supposedly that was the first-bad one per comment 9 based on nightly testing & a nightly that advertised itself as using that commit).  bors's immediately-following merge is in fact the first-bad commit: https://github.com/rust-lang/rust/commit/ff23ad3179014ba258f2b540fb39dd0f26852b7a
(In reply to Mike Hommey [:glandium] from comment #10)
> You can try https://github.com/rust-lang/cargo-bisect-rustc to bisect further.

Thanks. Using that tool to populate my available toolchains (and then selected the current toolchain as the default, and built Firefox, clobbering my objdir and sccache-dir each time).

From testing those builds, it actually seems that the artifact for commit `acbe4443c` is in fact "good" (supposedly that was the first-bad one per comment 9 based on nightly testing & a nightly that advertised itself as using that commit).  bors's immediately-following merge is in fact the first-bad commit: https://github.com/rust-lang/rust/commit/ff23ad3179014ba258f2b540fb39dd0f26852b7a
(In reply to Mike Hommey [:glandium] from comment #10)
> You can try https://github.com/rust-lang/cargo-bisect-rustc to bisect further.

Thanks. Using that tool to populate my available toolchains (and then selected the current toolchain as the default, and built Firefox, clobbering my objdir and sccache-dir each time).

From testing those builds, it actually seems that the artifact for commit `acbe4443c` is in fact "good" (supposedly that was the first-bad one per comment 8 - comment 9, based on rust-nightly testing & a nightly that advertised itself as using that commit).  bors's immediately-following merge is in fact the first-bad commit: https://github.com/rust-lang/rust/commit/ff23ad3179014ba258f2b540fb39dd0f26852b7a
(In reply to Mike Hommey [:glandium] from comment #10)
> You can try https://github.com/rust-lang/cargo-bisect-rustc to bisect further.

Thanks. Using that tool to populate my available toolchains (and then selected the current toolchain as the default, and built Firefox, clobbering my objdir and sccache-dir each time).

From testing those builds, it actually seems that the artifact for commit `acbe4443c` is in fact "good" (supposedly that was the first-bad one per comment 8 - comment 9, based on rust-nightly testing & a nightly that advertised itself as using that commit).  bors's immediately-following merge is in fact the first-bad commit when I test using cargo-bisect-rustc:
https://github.com/rust-lang/rust/commit/ff23ad3179014ba258f2b540fb39dd0f26852b7a

Back to Bug 1760743 Comment 11