Homu retry log - rust

Time (UTC) PR Message
2020-07-03 21:31:11 72978
@bors retry

seems like a network issue
2020-07-03 20:57:33 73650
@bors retry

network
2020-07-03 18:04:46 73650
@bors retry p=1000
2020-07-03 13:16:24 73985
@bors retry https://github.com/rust-lang/rust/issues/71988
2020-07-03 13:08:53 73650
@bors retry #73992 
2020-07-03 12:32:24 73881
@bors retry spurious
2020-07-03 12:18:21 73693
The command to re-run CI is
@bors retry
2020-07-03 12:17:55 73925
@bors retry
2020-07-03 12:17:28 73845
Second network failure in a row? Cc @rust-lang/infra
@bors retry
2020-07-03 11:25:40 73845
Network failures.
@bors retry
2020-07-03 11:21:08 73650
@bors retry network error
2020-07-02 08:35:50 73879
@bors retry yield
2020-07-02 08:35:24 73950
@bors retry
2020-07-02 08:26:31 73954
@bors retry

more network nonsense
2020-07-02 08:14:21 73950
@bors retry

This is happening pretty often, with different PRs in the rollup

@pietroalbini think this is an infra issue?
2020-07-02 03:36:24 73879
@bors retry yield
2020-07-02 02:38:12 73879
@bors retry yield
2020-07-02 01:44:33 73879
@bors retry yield
2020-07-02 01:44:26 73946
@bors retry yield
2020-07-02 01:44:14 73946
@bors retry yield
2020-07-01 20:13:45 72053
@bors retry yield retry
2020-07-01 20:06:18 73939
@bors retry

docker fail
2020-07-01 19:13:37 73882
@bors retry yield
2020-07-01 09:06:58 73885
@bors retry
2020-07-01 00:47:39 73706
@bors r=petrochenkov retry
2020-06-30 10:41:06 73884
@bors retry
2020-06-30 10:19:09 73884
@bors treeclosed=1000 r- retry

Need to make some infrastructure changes for a couple of minutes.
2020-06-29 12:03:45 73706
@bors retry
2020-06-29 12:00:26 73391
@bors retry
2020-06-28 23:43:29 73456
@bors retry

I'm going to presume this is spurious, I can't imagine a timeout caused by this PR.
2020-06-28 01:56:25 73823
@bors retry r- 

Dropped a PR to never roll up status.
2020-06-28 01:55:36 73800
@bors retry rollup=never

May have perf implications
2020-06-28 01:20:39 72437
@bors retry
2020-06-28 01:19:59 73823
@bors retry
2020-06-27 11:25:18 73790
@bors retry
2020-06-27 07:23:42 73766
@bors retry

network issues
2020-06-27 07:09:12 72437
@bors r- retry
2020-06-26 22:42:40 73596
@bors retry
2020-06-25 11:03:18 73711
retrying ... 

@bors retry 
2020-06-25 08:58:32 72559
@bors retry
2020-06-25 04:21:53 72700
@bors retry
2020-06-25 00:04:39 72700
uh 1 hour in.. but included it in a rollup.. so yielding.. 

@bors retry yield
2020-06-24 19:32:55 73418
@bors retry yield (will likely include this in a rollup after the clippy pr is merged)
2020-06-23 15:49:55 73613
@bors retry
2020-06-22 13:10:14 73415
@bors retry
The macOS x86_64 job inexplicably was running 2-3 times slower than normal (based on timing data).  No obvious hardware differences. 🤷 
2020-06-22 12:59:52 71660
included in rollup (accidentally two of them :P ) 

@bors retry 
2020-06-20 19:26:32 70946
going to retry again

@bors retry
2020-06-20 19:14:48 73550
@bors retry
2020-06-20 12:54:58 71911
@bors retry
2020-06-20 02:45:44 73506
@bors r=Xanewok retry
2020-06-19 23:04:07 73511
@bors retry force 

network
2020-06-19 22:54:53 73511
@bors retry
2020-06-19 19:32:24 73257
@bors retry yield
2020-06-19 19:31:31 73511
@bors retry

that's the byte order mark, that's a bug in the xsv tests
2020-06-19 16:27:28 73511
@bors retry

network issue
2020-06-19 16:16:35 73511
@bors retry
2020-06-19 16:16:16 73257
@bors retry yield
2020-06-19 12:30:15 71420
Yield.
@bors retry
2020-06-19 08:50:56 71420
@rust-lang/infra there's not even a build log at https://dev.azure.com/rust-lang/rust/_build/results?buildId=32326&view=logs&j=9121965e-722b-5094-4a33-f061e41958d8&t=64b964f2-043e-5afc-0fc3-c41881c5cd34 ? Is there any way to figure out what went wrong here?

@bors retry
2020-06-18 22:19:37 70946
@bors retry
2020-06-18 19:37:59 73446
@bors retry p=5
2020-06-18 19:08:19 73475
@bors retry
2020-06-18 18:38:24 73257
@bors retry
2020-06-18 12:03:32 73470
Build has failed without bors noticing
@bors retry
2020-06-18 08:30:53 73446
@bors retry
2020-06-18 08:30:38 73470
Second network failure in a row? Cc @rust-lang/infra
@bors retry
2020-06-18 08:14:04 73446
Yielding to rollup
@bors retry
2020-06-18 08:13:45 73470
Network failure.
@bors retry
2020-06-17 20:27:35 73065
@bors retry
2020-06-17 20:15:00 73455
@bors retry ceding to stable build
2020-06-17 14:53:36 73382
@bors retry
2020-06-16 07:17:07 73285
@bors retry
2020-06-16 05:05:47 73388
@bors retry
2020-06-15 07:35:29 71911
```
warning: spurious network error (2 tries remaining): failed to get 200 response from `https://crates.io/api/v1/crates/rand/0.5.5/download`, got 502
warning: spurious network error (1 tries remaining): failed to get 200 response from `https://crates.io/api/v1/crates/rand/0.5.5/download`, got 502
error: failed to download from `https://crates.io/api/v1/crates/rand/0.5.5/download`
```
@bors retry
2020-06-15 02:06:38 71911
@bors retry
2020-06-14 19:08:43 73340
@bors retry
2020-06-14 06:43:15 73089
@bors retry
2020-06-14 00:51:46 73326
@bors retry
2020-06-13 13:00:19 73313
Hm, good point. Let's try just the chalk PR then.
@bors retry r-
2020-06-13 12:52:36 72936
Yielding to rollup including this
@bors retry
2020-06-13 12:52:08 73313
OOM?
```
memory allocation of 268435456 bytes failed
error: Could not document `rustc_traits`.
```
Cc @rust-lang/infra is that something that happens occasionally?
@bors retry
2020-06-13 09:54:43 73311
@bors r- retry
2020-06-13 09:41:04 73309
@bors r- retry
2020-06-13 09:37:06 73299
Here: https://github.com/rust-lang-ci/rust/runs/767801939

@bors r- retry
2020-06-13 08:13:59 73089
@bors retry 

```
  failed to fetch `https://github.com/rust-lang/crates.io-index`
```
2020-06-13 00:55:53 65989
@bors retry
2020-06-13 00:55:30 72936
yielding to imp pr

@bors retry
2020-06-12 19:48:15 73238
@bors retry p=999

(just so that it runs automatically if things are fine, and doesn't if the tree remains closed)
2020-06-12 19:38:11 73262
@bors retry p=1000
2020-06-12 19:16:46 70946
@bors retry
2020-06-12 19:15:36 73262
@bors retry
2020-06-12 19:15:28 73262
@bors retry
2020-06-12 19:12:25 73238
@bors retry p=1000
2020-06-12 19:02:55 72936
For when the tree re-opens: @bors retry
2020-06-12 18:31:47 70946
@bors retry yield
2020-06-12 18:09:50 72936
@bors retry
2020-06-12 15:37:59 72936
@bors retry
2020-06-11 22:07:55 69478
@bors retry yield
2020-06-11 18:11:01 65989
@bors retry
2020-06-11 15:18:47 65989
@bors retry yield
2020-06-11 11:17:31 65989
@bors retry yield
2020-06-11 02:57:38 71896
@bors retry yield
2020-06-11 02:57:09 71896
@bors retry yield
2020-06-11 02:54:37 71896
@bors retry
2020-06-10 22:01:33 72897
@bors retry yield
2020-06-10 22:00:20 73206
@bors retry
2020-06-10 18:02:30 73213
@bors retry
2020-06-10 11:05:33 71896
@bors retry yield
2020-06-10 11:05:11 73206
@bors retry
2020-06-10 10:19:18 71896
Uh...

@bors retry
2020-06-10 09:13:14 73198
@bors retry yield
2020-06-10 09:12:58 73206
@bors retry (spurious)
2020-06-10 09:04:35 73198
@bors retry yield
2020-06-09 19:03:09 73168
@bors retry

(cc @rust-lang/infra on another timeout)
2020-06-09 18:58:38 73168
@bors retry
2020-06-09 13:41:41 72417
@bors retry (this pr is included in the rollup)
2020-06-08 16:32:46 73115
There we go.
@bors retry
2020-06-08 12:15:35 72655
@bors retry yield
2020-06-08 12:15:14 73115
@bors retry
2020-06-08 11:07:19 72571
@bors retry
2020-06-08 07:56:21 72026
Yielding to rollup containing this
@bors retry
2020-06-07 14:14:29 72904
@bors retry
2020-06-07 00:34:42 72904
@bors retry

@bors r-
2020-06-06 19:58:23 71796
@bors retry rollup=always
2020-06-06 17:06:15 71796
@bors retry
2020-06-06 14:47:30 71796
yield
@bors retry
2020-06-06 08:12:19 72927
No logs?
Looks like the "Run build" stage haven't even started.
Looks spurious.
@bors retry
2020-06-06 01:05:29 72357
@bors retry yield
2020-06-05 15:20:58 72982
@bors retry yield
2020-06-05 15:20:43 73025
looks spurious

@bors retry 
2020-06-05 11:30:52 72571
@bors retry
2020-06-05 11:11:23 72957
@bors retry 
2020-06-04 19:31:54 72508
@bors retry yield
2020-06-04 18:27:26 72984
spurious .... 

@bors retry
2020-06-04 11:38:15 72655
@bors retry
2020-06-04 10:17:33 72708
@bors retry yield
2020-06-03 20:09:13 72754
@bors retry yield
2020-06-03 16:06:25 72754
@bors retry yield 
2020-06-03 09:20:48 72586
@bors retry
2020-06-03 01:00:33 72618
@bors retry
2020-06-02 19:35:13 72508
@bors retry
2020-06-02 17:59:09 72586
@bors retry
2020-06-02 16:30:40 72618
@bors retry yield
2020-06-02 04:10:43 72903
This contains #72417 which breaks rls build.
@bors retry r-
2020-06-01 05:21:40 72844
@bors retry
2020-05-30 21:23:13 72116
@bors retry
2020-05-30 17:44:24 72116
@bors retry yield
2020-05-30 12:49:42 72743
@bors retry
2020-05-30 11:46:18 72116
Spurious?
```
curl: (56) SSLRead() return error -9806
clang+llvm-9.0.0-x86_64-darwin-apple/bin/llc: Lzma library error:  No progress is possible
tar: Error exit delayed from previous errors.
```
@bors retry
2020-05-30 07:56:01 72768
@bors retry
2020-05-30 03:40:43 72116
@bors retry yield
2020-05-29 19:50:16 72116
queue is long so yielding ( a bit late ) 

@bors retry 
2020-05-29 15:01:35 67460
@bors retry yield
2020-05-29 00:42:52 72506
@bors retry yield
2020-05-28 19:02:42 72506
@bors retry yield
2020-05-28 17:38:26 72681
Since the previous macOS build was successful, I'd say it's spurious:
```
failures:

---- [run-make] run-make-fulldeps/long-linker-command-lines stdout ----

error: make failed
status: exit code: 2
command: "make"
stdout:
------------------------------------------
DYLD_LIBRARY_PATH="/Users/runner/runners/2.168.2/work/1/s/build/x86_64-apple-darwin/test/run-make-fulldeps/long-linker-command-lines/long-linker-command-lines:/Users/runner/runners/2.168.2/work/1/s/build/x86_64-apple-darwin/stage2/lib:" '/Users/runner/runners/2.168.2/work/1/s/build/x86_64-apple-darwin/stage2/bin/rustc' --out-dir /Users/runner/runners/2.168.2/work/1/s/build/x86_64-apple-darwin/test/run-make-fulldeps/long-linker-command-lines/long-linker-command-lines -L /Users/runner/runners/2.168.2/work/1/s/build/x86_64-apple-darwin/test/run-make-fulldeps/long-linker-command-lines/long-linker-command-lines  foo.rs -g -O
RUSTC="/Users/runner/runners/2.168.2/work/1/s/build/x86_64-apple-darwin/stage2/bin/rustc" DYLD_LIBRARY_PATH="/Users/runner/runners/2.168.2/work/1/s/build/x86_64-apple-darwin/test/run-make-fulldeps/long-linker-command-lines/long-linker-command-lines:/Users/runner/runners/2.168.2/work/1/s/build/x86_64-apple-darwin/stage2/lib/rustlib/x86_64-apple-darwin/lib:" /Users/runner/runners/2.168.2/work/1/s/build/x86_64-apple-darwin/test/run-make-fulldeps/long-linker-command-lines/long-linker-command-lines/foo
attempt: 100
attempt: 200
attempt: 300

------------------------------------------
stderr:
------------------------------------------
warning: variable does not need to be mutable
  --> foo.rs:93:13
   |
93 |         for mut arg in linker_args.split('S') {
   |             ----^^^
   |             |
   |             help: remove this `mut`
   |
   = note: `#[warn(unused_mut)]` on by default

warning: 1 warning emitted

thread 'main' panicked at 'status: exit code: 1
stdout:

stderr:
error: could not exec the linker `/Users/runner/runners/2.168.2/work/1/s/build/x86_64-apple-darwin/test/run-make-fulldeps/long-linker-command-lines/long-linker-command-lines/foo`
  |

', foo.rs:76:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
make: *** [all] Error 101
```

@bors retry
2020-05-28 11:32:35 72681
@bors retry
2020-05-28 09:53:13 72671
Seems spurious:
```
##[warning]Received request to deprovision: The request was cancelled by the remote provider.
,##[error]We stopped hearing from agent Azure Pipelines 4. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. For more information, see: https://go.microsoft.com/fwlink/?linkid=846610
Agent: Azure Pipelines 4
```

@bors retry
2020-05-27 11:18:50 72601
@bors retry yield
2020-05-27 10:42:11 72639
@bors retry
2020-05-27 01:03:53 72103
@bors retry yield
2020-05-25 22:04:39 71487
@bors retry yield
2020-05-25 20:20:37 72571
Let's see how 14 cores perform.

@bors retry
2020-05-25 18:05:47 72571
@bors retry
2020-05-25 14:30:08 72571
@bors retry
2020-05-25 14:07:03 72571
@bors retry
2020-05-25 13:55:28 72571
@bors retry
2020-05-25 13:35:35 72571
@bors retry
2020-05-23 14:21:59 72501
This will fail due to https://github.com/rust-lang/rust/pull/72400.
@bors r- retry
2020-05-23 14:07:00 72362
@bors retry yield
2020-05-23 04:41:21 72478
@bors retry
2020-05-22 20:24:52 72362
@bors retry
2020-05-22 20:24:07 72393
@bors retry
2020-05-22 20:14:30 72388
@bors retry
2020-05-22 19:53:29 72362
@bors retry 
2020-05-22 19:53:12 72478
spurious

@bors retry 
2020-05-22 19:48:22 72362
@bors retry yield
2020-05-22 15:33:28 72256
@bors retry (yield)
2020-05-22 14:56:59 72123
@bors rollup retry
yielding