Homu retry log - rust

Time (UTC) PR Message
2019-10-14 16:05:58 65252
@bors retry azure network error
2019-10-14 16:05:26 65170
@bors retry azure network error
2019-10-14 15:52:22 64987
@bors retry
2019-10-14 13:55:23 64987
@bors retry rolled up.
2019-10-14 10:00:48 65399
@bors retry
2019-10-13 21:37:02 62655
@bors r- retry
2019-10-13 21:35:35 65385
@bors retry try
2019-10-13 18:13:14 65342
@bors retry
2019-10-13 17:18:50 65214
@bors retry rolled up.
2019-10-13 15:20:15 65214
@bors retry rolled up.
2019-10-12 19:42:41 65342
cc @burntsushi -- I doubt the failure above is due to this PR so maybe a legitimate (if accidental) discovery of a problem with an older version of xsv's tests? https://rust-lang.github.io/rust-log-analyzer/log-viewer/#https://dev.azure.com/rust-lang/e71b0ddf-dd27-435a-873c-e30f86eea377/_apis/build/builds/10564/logs/1048

@bors retry
2019-10-12 16:03:25 65328
@bors retry prioritizing nightly breakage fix
2019-10-12 03:51:56 65322
@bors retry
2019-10-11 22:12:07 65020
@bors retry yielding to rollup
2019-10-11 06:58:50 65299
Seems the 16 PR rollup was included as well? @bors r- retry
2019-10-11 06:02:57 65190
@bors retry
2019-10-11 03:38:03 65190
@bors retry
have to r+ the rollup first...
2019-10-11 03:37:24 65190
@bors retry yielding to rollup
2019-10-09 03:32:16 64656
@bors retry rolled up.
2019-10-09 01:43:57 64656
@bors retry rolled up.
2019-10-08 21:32:02 64284
@bors retry rolled up.
2019-10-08 12:47:05 62655
@bors r- retry
2019-10-07 16:15:25 61430
Seems spurious: a segfault installing awscli:
```
Script contents:
src/ci/install-awscli.sh
========================== Starting Command Output ===========================
[command]/bin/bash --noprofile --norc /home/vsts/work/_temp/7e1f4ab8-5218-4d32-8794-b923dc0cf857.sh
Reading package lists...
Building dependency tree...
Reading state information...
Suggested packages:
  python-setuptools-doc
The following NEW packages will be installed:
  python3-setuptools
0 upgraded, 1 newly installed, 0 to remove and 22 not upgraded.
E: Method http has died unexpectedly!
E: Sub-process http received a segmentation fault.
E: Method /usr/lib/apt/methods/http did not start correctly
##[error]Bash exited with code '100'.
##[section]Finishing: Install awscli
```

@bors retry
2019-10-07 08:40:49 64780
@bors retry
2019-10-07 03:49:16 64739
@bors retry rolled up.
2019-10-06 04:59:12 65139
@alex thanks for pointing that out. I've reverted the emscripten change and am going to close this rollup in favor of another that includes the revert.

@bors retry yielding to #65152 
@bors r-
2019-10-06 01:52:53 65139
Looks like this succeeded, but timed out... @bors retry
2019-10-05 21:01:47 64909
@bors retry
2019-10-05 20:20:39 64765
@bors retry rolled up
2019-10-05 05:11:51 65115
@bors retry 
2019-10-04 18:17:06 64909
@bors retry yielding to rollup including this PR https://github.com/rust-lang/rust/pull/65109
2019-10-03 23:29:44 61879
@bors retry
2019-10-03 23:11:34 61879
@bors retry rolled up
2019-10-03 21:05:00 61879
@bors retry rolled up.
2019-10-03 20:16:50 61879
@bors retry rolled up.
2019-10-03 12:19:18 64690
@bors retry -- prioritizing other PRs to see which one caused failure in https://github.com/rust-lang/rust/pull/65053#issuecomment-537916050 :(
2019-10-03 11:00:13 64936
@bors retry
2019-10-03 06:52:40 64749
@bors retry
2019-10-03 06:05:03 64941
@bors retry rolled up.
2019-10-03 02:08:49 63678
@bors retry rolled up.
2019-10-02 23:55:17 64906
@bors retry
2019-10-02 22:40:28 64749
@bors retry
2019-10-02 06:08:20 64952
@bors retry rolled up
2019-10-01 18:59:03 64952
@bors retry rolled up

Also: The homu queue page says it's building this PR, but I don't see any comment here that it's building or a build in the azure queue.
2019-10-01 18:55:34 64952
@bors retry rolled up

Also: The homu queue page says it's building this PR but I don't see any comment here that it's building.
2019-10-01 18:55:26 64952
@bors retry rolled up

Also: The queue page says it's building this PR but I don't see any comment here that it's building.
2019-10-01 18:54:14 64952
@bors retry rolled up

Also: bors seems stuck, the queue page says it's building this PR but I don't see any notification here that it's building.
2019-10-01 17:45:06 64936
@bors try retry
2019-10-01 14:11:17 64952
@bors retry rolled up.
2019-10-01 12:22:35 64404
@bors retry rolled up.
2019-10-01 12:07:46 64404
@bors retry rolled up.
2019-10-01 11:54:12 64922
@bors retry
2019-10-01 07:56:47 63649
@bors retry
2019-10-01 06:20:57 63649
@bors retry rolled up.
2019-10-01 02:31:45 63649
@bors retry yielding to timed out r0llup.
2019-10-01 02:31:17 64932
@bors retry
2019-09-30 21:40:06 63649
Yielding to rollup, this hasn't passed CI checks yet.

@bors retry
2019-09-30 19:15:39 64838
@bors retry rolled up
2019-09-30 17:55:00 64850
@bors retry
2019-09-29 18:34:59 64901
@bors r- retry (https://github.com/rust-lang/rust/pull/64896#issuecomment-536327452)
2019-09-29 17:45:17 64691
@bors retry rolled up.
2019-09-28 09:19:15 64419
@bors retry rolled up... (don't ask why...)
2019-09-28 07:31:35 64419
Yielding prio to https://github.com/rust-lang/rust/pull/64868 and not including this one because it has failed too much.

@bors retry rollup=never p=1
2019-09-28 03:38:41 63492
@bors retry
2019-09-28 01:22:56 63492
@bors retry rolled up.
2019-09-26 20:29:37 64813
@bors r- retry ^--
2019-09-26 20:29:07 64816
@bors retry
2019-09-26 02:41:59 64513
@bors retry rolled up.
2019-09-25 14:27:03 62975
@bors retry rolled up.
2019-09-25 14:25:46 64508
@bors retry can break toolstate again.
2019-09-25 01:49:42 64324
@bors retry rolled up.
2019-09-24 21:46:22 63934
@bors retry rolled up.
2019-09-24 18:26:39 63948
@crlf0710 Did you try this locally with a full `./x.py test` to see if you could reproduce the problem?

Let's try this again and see if rebasing changed anything (I don't think so, but worth a shot...)

@bors retry
2019-09-24 10:58:37 64428
@bors retry prioritizing stabilization PR.
2019-09-24 10:57:20 64733
@bors retry
2019-09-24 10:53:17 64428
@bors retry rolled up.
2019-09-23 21:14:11 64709
Gah!

@bors retry 
2019-09-23 08:05:11 64308
@bors r- retry
2019-09-23 08:05:03 64072
@bors r- retry
2019-09-21 22:30:41 64661
@bors retry
2019-09-21 20:51:46 63948
@bors retry rollup=never p=1
2019-09-21 14:01:57 64657
@bors retry r-
2019-09-21 14:00:14 64010
@bors retry
2019-09-21 01:20:46 64047
@bors retry rolled up
2019-09-20 23:37:47 64645
@bors retry
Closing in favor of #64646 
2019-09-20 23:31:39 64316
@bors retry yielding to rollup
2019-09-19 22:41:43 64616
@bors retry
2019-09-19 16:13:02 63448
@bors retry
2019-09-19 14:00:12 64595
Huh. @bors retry spurious "The user-provided path cpu-usage.csv does not exist. " hopefully?
2019-09-19 02:54:06 64151
@bors retry
2019-09-19 01:17:17 64151
@bors retry rolled up.
2019-09-18 18:07:05 64576
@bors retry

Copied the wrong GitHub token, woops! Updated the variable group on the Azure Pipelines side.
2019-09-18 17:58:41 64348
@bors retry rolled up
2019-09-18 04:28:57 64486
@bors retry rolled up
2019-09-18 02:18:54 64486
@bors retry rolled up
2019-09-17 14:30:39 64517
@bors: retry

* https://github.com/rust-lang/rust/issues/64551
2019-09-17 01:09:03 64085
@bors retry rolled up.
2019-09-16 21:22:50 64485
@bors retry rolled up.
2019-09-16 21:18:37 64522
@bors r- retry
linkcheck failed in https://github.com/rust-lang/rust/pull/64516
2019-09-16 19:41:13 64485
@bors retry rolled up.
2019-09-16 11:49:42 64451
@bors retry

Spurious network failure.
2019-09-16 10:26:05 64381
@bors retry
2019-09-14 20:16:50 64290
@bors retry rolled up.
2019-09-14 18:57:27 64290
@bors retry rolled up.
2019-09-14 14:43:28 64203
@bors retry rolled up.
2019-09-14 12:31:27 64290
@bors retry rolled up.
2019-09-14 10:22:27 64290
@bors retry rolled up.
2019-09-14 00:21:18 64438
It specifically failed in Linux x86_64-gnu-aux, but for some reason I can't get the logs. Maybe azure tripped up somehow?

@bors retry
2019-09-13 08:28:31 64254
@bors retry
2019-09-12 03:28:55 64303
Not sure about that timeout. Let's try again.

@bors retry
2019-09-11 13:18:29 64154
@bors: retry

Looks like a normal timeout, but let's see if it's affected by this..
2019-09-11 00:39:33 64060
@bors retry rolled up
2019-09-10 22:27:54 64060
@bors retry rolled up
2019-09-10 21:37:56 64060
@bors retry rolled up
2019-09-10 04:30:28 64307
@bors retry rolled up.

Testing out @tmandry's idea.
2019-09-10 00:34:26 64321
@bors retry
2019-09-09 20:18:35 64279
@bors retry rolled up.
2019-09-09 19:59:30 63806
@bors: retry
2019-09-08 20:51:18 64078
@bors retry rolled up.
2019-09-08 13:02:51 62205
@bors retry rolled up.
2019-09-08 13:02:24 64281
@bors retry Spurious network.
2019-09-08 10:12:57 62205
@bors retry rolled up.
2019-09-07 22:08:25 64052
@bors retry rolled up.
2019-09-07 18:02:17 64023
@bors retry rolled up.
2019-09-07 10:22:55 64246
@bors retry
2019-09-07 06:07:25 63919
@bors retry rolled up.
2019-09-06 17:03:07 63565
@bors retry rolled up.
2019-09-06 07:37:35 63676
@bors retry rolled up.
2019-09-06 00:57:26 64171
@bors retry prioritize rollup
2019-09-06 00:56:51 64182
@bors retry r-

Creating a larger rollup which'll subsume this one
2019-09-06 00:54:04 64171
@bors retry prioritize rollup
2019-09-06 00:53:50 64182
@bors retry
2019-09-05 20:39:37 64182
@bors retry
2019-09-05 19:08:53 64171
@bors retry network error
2019-09-05 07:33:39 62848
@bors retry rolled up.
2019-09-05 07:25:15 62800
@bors retry probably spurious
2019-09-05 06:07:25 62848
@bors retry rolled up.
2019-09-05 02:11:02 62848
@bors retry prioritizing r0llup since queue is really long.
2019-09-04 19:40:49 64108
@bors retry
2019-09-04 16:32:09 63880
@bors r- retry
2019-09-04 16:31:57 63941
@bors r- retry
2019-09-04 16:31:49 63956
@bors r- retry
2019-09-04 00:52:38 64051
@bors retry
2019-09-03 10:23:21 64044
@bors retry
2019-09-02 17:12:37 64049
```
Dist cargo stage1 (mips64el-unknown-linux-gnuabi64)
Building stage1 tool cargo (mips64el-unknown-linux-gnuabi64)
 Downloading‌ crates ...‌
error:‌ failed to download from `https://crates.io/api/v1/crates/openssl-src/111.3.0+1.1.1c/download`‌

Caused by:
  [35] SSL connect error (error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure)
command did not execute successfully: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "--target" "mips64el-unknown-linux-gnuabi64" "-Zdual-proc-macros" "-Zbinary-dep-depinfo" "-j" "2" "--release" "--locked" "--color" "always" "--manifest-path" "/checkout/src/tools/cargo/Cargo.toml" "--features" "rustc-workspace-hack/all-static" "--message-format" "json-render-diagnostics"
expected success, got: exit code: 101
failed to run: /checkout/obj/build/bootstrap/debug/bootstrap dist --host mips64el-unknown-linux-gnuabi64 --target mips64el-unknown-linux-gnuabi64
Build completed unsuccessfully in 1:18:54
```

@bors retry
2019-09-02 16:59:43 64001
@bors retry
2019-09-02 11:03:58 64001
Spurious network issue:
```
2019-09-02T07:41:17.8650159Z Downloading crates ...
2019-09-02T07:41:18.1047208Z error: failed to download from `https://crates.io/api/v1/crates/openssl-src/111.3.0+1.1.1c/download` 
```
@bors retry