You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As seen in rust-lang/rust#80101 (comment), cargo-bisect-rustc seems to have produced an incorrect result. Additionally, it seemed to be installing a commit then skipped to a different one and then another without printing any information. And it checked a commit twice (cc #85).
Here's the full log from my usage of cargo-bisect-rustc in case it helps in diagnosing the problem:
(pnkfelix note: Of course, everywhere you see ==> No is a spot where the author chose "mark baseline", and ==> Yes means the choice was "mark regressed")
❯ cargo bisect-rustc --preserve --prompt --start=2020-11-17 --end=2020-11-20 -- doc --document-private-itemsinstalling nightly-2020-11-17testing... Documenting foo v0.1.0 (/Users/user/rust-issues/rust-issue-80101) Finished dev [unoptimized + debuginfo] target(s) in 8.72snightly-2020-11-17 finished with exit code Some(0).please select an action to take:RESULT: nightly-2020-11-17, ===> Noinstalling nightly-2020-11-20testing... Documenting foo v0.1.0 (/Users/user/rust-issues/rust-issue-80101) Finished dev [unoptimized + debuginfo] target(s) in 8.04snightly-2020-11-20 finished with exit code Some(0).please select an action to take:RESULT: nightly-2020-11-20, ===> Yesinstalling nightly-2020-11-18testing... Documenting foo v0.1.0 (/Users/user/rust-issues/rust-issue-80101) Finished dev [unoptimized + debuginfo] target(s) in 10.66snightly-2020-11-18 finished with exit code Some(0).please select an action to take:RESULT: nightly-2020-11-18, ===> Noinstalling nightly-2020-11-19testing... Documenting foo v0.1.0 (/Users/user/rust-issues/rust-issue-80101) Finished dev [unoptimized + debuginfo] target(s) in 9.87snightly-2020-11-19 finished with exit code Some(0).please select an action to take:RESULT: nightly-2020-11-19, ===> Yessearched toolchains nightly-2020-11-17 through nightly-2020-11-20********************************************************************************Regression in nightly-2020-11-19********************************************************************************fetching https://static.rust-lang.org/dist/2020-11-18/channel-rust-nightly-git-commit-hash.txtnightly manifest 2020-11-18: 40 B / 40 B [================] 100.00 % 43.49 KB/s converted 2020-11-18 to c919f490bbcd2b29b74016101f7ec71aaa24bdbbfetching https://static.rust-lang.org/dist/2020-11-19/channel-rust-nightly-git-commit-hash.txtnightly manifest 2020-11-19: 40 B / 40 B [=================] 100.00 % 1.14 MB/s converted 2020-11-19 to 8256379832b5ecb7f71e8c5e2018446482223c12looking for regression commit between 2020-11-18 and 2020-11-19opening existing repository at "/Users/user/rust"refreshing repositoryfetching (via local git) commits from c919f490bbcd2b29b74016101f7ec71aaa24bdbb to 8256379832b5ecb7f71e8c5e2018446482223c12opening existing repository at "/Users/user/rust"refreshing repositorylooking up first commitlooking up second commitchecking that commits are by bors and thus have ci artifacts...finding bors merge commitsfound 6 bors merge commits in the specified range commit[0] 2020-11-17UTC: Auto merge of #79138 - m-ou-se:rollup-owel5ld, r=m-ou-se commit[1] 2020-11-18UTC: Auto merge of #79132 - pietroalbini:beta-next, r=Mark-Simulacrum commit[2] 2020-11-18UTC: Auto merge of #77820 - jyn514:from-inner, r=petrochenkov commit[3] 2020-11-18UTC: Auto merge of #79159 - pietroalbini:woops, r=pietroalbini commit[4] 2020-11-18UTC: Auto merge of #79167 - m-ou-se:rollup-4g15apk, r=m-ou-se commit[5] 2020-11-18UTC: Auto merge of #78995 - Nadrieril:clean-empty-match, r=varkorvalidated commits found, specifying toolchainsinstalling c919f490bbcd2b29b74016101f7ec71aaa24bdbbtesting... Documenting foo v0.1.0 (/Users/user/rust-issues/rust-issue-80101) Finished dev [unoptimized + debuginfo] target(s) in 10.60sc919f490bbcd2b29b74016101f7ec71aaa24bdbb finished with exit code Some(0).please select an action to take:RESULT: c919f490bbcd2b29b74016101f7ec71aaa24bdbb, ===> Noinstalling 8256379832b5ecb7f71e8c5e2018446482223c12testing... Documenting foo v0.1.0 (/Users/user/rust-issues/rust-issue-80101) Finished dev [unoptimized + debuginfo] target(s) in 13.33s8256379832b5ecb7f71e8c5e2018446482223c12 finished with exit code Some(0).please select an action to take:RESULT: 8256379832b5ecb7f71e8c5e2018446482223c12, ===> Yesinstalling c4f836ad1aceb83507810d9499f56988fd24578dinstalling 87776d7d5322422e5239e153e793b687f7f9c379installing 7d747db0d5dd8f08f2efb073e2e77a34553465a7testing... Documenting foo v0.1.0 (/Users/user/rust-issues/rust-issue-80101) Finished dev [unoptimized + debuginfo] target(s) in 8.63s7d747db0d5dd8f08f2efb073e2e77a34553465a7 finished with exit code Some(0).please select an action to take:RESULT: 7d747db0d5dd8f08f2efb073e2e77a34553465a7, ===> Yesinstalling c919f490bbcd2b29b74016101f7ec71aaa24bdbbtesting... Documenting foo v0.1.0 (/Users/user/rust-issues/rust-issue-80101) Finished dev [unoptimized + debuginfo] target(s) in 8.58sc919f490bbcd2b29b74016101f7ec71aaa24bdbb finished with exit code Some(0).please select an action to take:RESULT: c919f490bbcd2b29b74016101f7ec71aaa24bdbb, ===> Nosearched toolchains c919f490bbcd2b29b74016101f7ec71aaa24bdbb through 8256379832b5ecb7f71e8c5e2018446482223c12********************************************************************************Regression in 7d747db0d5dd8f08f2efb073e2e77a34553465a7********************************************************************************=================================================================================== Please file this regression report on the rust-lang/rust GitHub repository == New issue: https://github.com/rust-lang/rust/issues/new == Known issues: https://github.com/rust-lang/rust/issues == Copy and paste the text below into the issue report thread. Thanks! ===================================================================================searched nightlies: from nightly-2020-11-17 to nightly-2020-11-20regressed nightly: nightly-2020-11-19searched commits: from https://github.com/rust-lang/rust/commit/c919f490bbcd2b29b74016101f7ec71aaa24bdbb to https://github.com/rust-lang/rust/commit/8256379832b5ecb7f71e8c5e2018446482223c12regressed commit: https://github.com/rust-lang/rust/commit/7d747db0d5dd8f08f2efb073e2e77a34553465a7<details><summary>bisected with <a href='https://github.com/rust-lang/cargo-bisect-rustc'>cargo-bisect-rustc</a> v0.6.0</summary>Host triple: x86_64-apple-darwinReproduce with:```bashcargo bisect-rustc --preserve --prompt --start=2020-11-17 --end=2020-11-20 -- doc --document-private-items ```</details>
Note that the issue seems to be when bisecting CI artifacts; I think it's right about which nightly the issue is in. Also note that I was manually testing with --prompt because I was bisecting a visual rustdoc regression. However, I bisected three times and got the same result, so I think it's unlikely that it's human error.
The text was updated successfully, but these errors were encountered:
Seems like it's potentially an off-by-one error since the commit that actually regressed was one later than the one cargo-bisect-rustc thought – the correct one was rust-lang/rust@c4f836a.
As seen in rust-lang/rust#80101 (comment), cargo-bisect-rustc seems to have produced an incorrect result. Additionally, it seemed to be installing a commit then skipped to a different one and then another without printing any information. And it checked a commit twice (cc #85).
Here's the full log from my usage of cargo-bisect-rustc in case it helps in diagnosing the problem:
(pnkfelix note: Of course, everywhere you see
==> No
is a spot where the author chose "mark baseline", and==> Yes
means the choice was "mark regressed")Note that the issue seems to be when bisecting CI artifacts; I think it's right about which nightly the issue is in. Also note that I was manually testing with
--prompt
because I was bisecting a visual rustdoc regression. However, I bisected three times and got the same result, so I think it's unlikely that it's human error.The text was updated successfully, but these errors were encountered: