rust-lang / rust-lang/cargo-bisect-rustc

Nightly can be checked thrice in certain cases

Open
#85 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-bisection-algorithm bug
Dominant language
Rust
Stars
206
Forks
60
PR merge metrics
No merged PRs in 30d

Description

$ cargo-bisect-rustc --end=2020-05-09
installing nightly-2020-05-09
RESULT: nightly-2020-05-09, ===> Yes
uninstalling nightly-2020-05-09

installing nightly-2020-05-07
RESULT: nightly-2020-05-07, ===> Yes
uninstalling nightly-2020-05-07

installing nightly-2020-05-05
RESULT: nightly-2020-05-05, ===> Yes
uninstalling nightly-2020-05-05

installing nightly-2020-05-03
RESULT: nightly-2020-05-03, ===> No
uninstalling nightly-2020-05-03

installing nightly-2020-05-05
RESULT: nightly-2020-05-05, ===> Yes
uninstalling nightly-2020-05-05

installing nightly-2020-05-04
RESULT: nightly-2020-05-04, ===> No
uninstalling nightly-2020-05-04

searched toolchains nightly-2020-05-03 through nightly-2020-05-05
installing nightly-2020-05-05
uninstalling nightly-2020-05-05


********************************************************************************
Regression in nightly-2020-05-05
********************************************************************************

As you can see, 2020-05-05 is downloaded and tested thrice. Is that necessary?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides no file or test paths; start at the cargo-bisect-rustc command's nightly-selection and checking flow, reproducing the shown --end=2020-05-09 run. Trace why nightly-2020-05-05 is installed and tested three times; done means the repeated checks are understood and unnecessary repetition is avoided.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.