Skip to content

Instantly share code, notes, and snippets.

@toku-sa-n
Created September 24, 2020 03:12
Show Gist options
  • Save toku-sa-n/0b8e18d78c625ee1dd6b9fe630bed7ce to your computer and use it in GitHub Desktop.
Save toku-sa-n/0b8e18d78c625ee1dd6b9fe630bed7ce to your computer and use it in GitHub Desktop.
stdin
checking nightly-2020-09-23 from the currently installed default nightly toolchain as the last failure
installing nightly-2020-09-23
testing...
RESULT: nightly-2020-09-23, ===> Yes
installing nightly-2020-09-21
testing...
RESULT: nightly-2020-09-21, ===> No
installing nightly-2020-09-23
testing...
RESULT: nightly-2020-09-23, ===> Yes
installing nightly-2020-09-22
testing...
RESULT: nightly-2020-09-22, ===> No
searched toolchains nightly-2020-09-21 through nightly-2020-09-23
installing nightly-2020-09-23
testing...
********************************************************************************
Regression in nightly-2020-09-23
********************************************************************************
fetching https://static.rust-lang.org/dist/2020-09-22/channel-rust-nightly-git-commit-hash.txt
nightly manifest 2020-09-22: 32 B / 40 B [==========>--] 80.00 % 486.51 KB/s 0s nightly manifest 2020-09-22: 40 B / 40 B [===============] 100.00 % 501.95 KB/s converted 2020-09-22 to fb1dc34a831688f8eca89ea22ea2eb39e881d729
fetching https://static.rust-lang.org/dist/2020-09-23/channel-rust-nightly-git-commit-hash.txt
nightly manifest 2020-09-23: 32 B / 40 B [===========>---] 80.00 % 4.88 MB/s 0s nightly manifest 2020-09-23: 40 B / 40 B [=================] 100.00 % 2.36 MB/s converted 2020-09-23 to 0da58007451a154da2480160429e1604a1f5f0ec
looking for regression commit between 2020-09-22 and 2020-09-23
opening existing repository at "rust.git"
refreshing repository
fetching (via local git) commits from fb1dc34a831688f8eca89ea22ea2eb39e881d729 to 0da58007451a154da2480160429e1604a1f5f0ec
opening existing repository at "rust.git"
refreshing repository
looking up first commit
looking up second commit
checking that commits are by bors and thus have ci artifacts...
finding bors merge commits
found 9 bors merge commits in the specified range
commit[0] 2020-09-21UTC: Auto merge of #77003 - joshtriplett:remove-duplicate-link-libraries, r=Mark-Simulacrum
commit[1] 2020-09-21UTC: Auto merge of #76683 - simonvandel:inst-combine-deref, r=oli-obk
commit[2] 2020-09-22UTC: Auto merge of #76913 - vandenheuvel:performance_debug, r=lcnr
commit[3] 2020-09-22UTC: Auto merge of #77039 - ecstatic-morse:rollup-qv3jj4a, r=ecstatic-morse
commit[4] 2020-09-22UTC: Auto merge of #76799 - Mark-Simulacrum:fix-cross-compile-dist, r=alexcrichton
commit[5] 2020-09-22UTC: Auto merge of #76906 - Nicholas-Baron:shorten_typeck_check, r=oli-obk
commit[6] 2020-09-22UTC: Auto merge of #76626 - jyn514:x.py-changelog, r=Mark-Simulacrum
commit[7] 2020-09-22UTC: Auto merge of #76110 - FedericoPonzi:convert-openoptions-cint, r=JoshTriplett
commit[8] 2020-09-22UTC: Auto merge of #76810 - Mark-Simulacrum:fix-lld-macos, r=alexcrichton
validated commits found, specifying toolchains
installing fb1dc34a831688f8eca89ea22ea2eb39e881d729
testing...
RESULT: fb1dc34a831688f8eca89ea22ea2eb39e881d729, ===> No
installing 0da58007451a154da2480160429e1604a1f5f0ec
testing...
RESULT: 0da58007451a154da2480160429e1604a1f5f0ec, ===> No
ERROR: the commit at the end of the range (0da58007451a154da2480160429e1604a1f5f0ec) does not reproduce the regression
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment