Homu retry log - rust

Time (UTC) PR Message
2019-08-22 18:06:28 63807
@bors retry
2019-08-22 06:14:45 63175
@bors retry
2019-08-21 07:35:07 63165
@bors retry r-
2019-08-21 07:34:56 63517
@bors retry r-
2019-08-19 20:49:35 63252
@bors retry rolled up.
2019-08-19 17:04:06 63252
@bors retry yielding prio to lockfile PR.
2019-08-18 13:22:35 61626
I believe this failed in https://github.com/rust-lang/rust/pull/63683#issuecomment-522321479, @bors r- retry
2019-08-17 09:14:33 63505
@bors retry rolled up.
2019-08-17 01:04:31 63175
@bors retry
2019-08-16 22:11:21 63175
@bors retry rolled up.
2019-08-16 12:18:55 63470
@bors retry

Pretty sure literally every builder passed and homu just didn't get the notification (cc @pietroalbini - does that look similar to https://github.com/rust-lang/rust/issues/63513?)
2019-08-15 22:30:55 63470
@bors retry spurious
2019-08-15 17:47:07 63173
@bors retry
2019-08-15 17:15:15 63173
@bors retry rolled up.
2019-08-15 16:37:35 63173
@bors retry rolled up.
2019-08-15 12:34:59 63155
@bors retry rolled up.
2019-08-15 10:21:55 63155
@bors retry rolled up.
2019-08-14 18:42:10 63534
@bors retry rolled up
2019-08-14 16:30:03 63534
@bors retry rolled up
2019-08-14 14:58:29 63534
@bors p=1 retry rolled up.
2019-08-14 14:52:50 63534
@bors retry
2019-08-14 07:06:55 63350
@bors retry r-
2019-08-14 07:06:46 63465
@bors retry r-
2019-08-14 02:20:09 62849
@bors retry rolled up.
2019-08-14 00:39:02 63540
@bors retry -- added some more stuff in https://github.com/rust-lang/rust/pull/63541 and dropped RLS (don't want to risk it with the current queue length!)
2019-08-14 00:27:42 63517
@bors retry and closing (prioritize https://github.com/rust-lang/rust/pull/63540)
2019-08-13 23:56:44 63517
@bors retry
2019-08-13 16:11:55 63517
@bors retry Prioritizing master=>beta promotion.
2019-08-13 15:42:09 63517
@bors retry

The build actually failed due to a spurious network error, but Azure Pipelines failed to report the status. https://github.com/rust-lang/rust/issues/63513
2019-08-13 12:05:52 62849
@bors retry rolled up (oops, forgot to adjust prio)
2019-08-13 12:05:08 62849
@bors retry rolled up.
2019-08-13 06:25:47 63498
@bors retry 
2019-08-13 00:47:28 63503
@bors retry -- stable release priority
2019-08-12 21:52:21 63503
@bors retry -- stable release priority
2019-08-12 21:51:44 63498
@bors retry lets hope this is spurious...
2019-08-12 19:41:53 63485
@bors retry prioritize stable
2019-08-12 19:22:29 63485
@bors retry

Spurious crates.io download failure (expired cert)
2019-08-12 08:58:44 62108
@bors retry rolled up.
2019-08-12 06:57:45 62108
@bors retry rolled up.
2019-08-11 19:19:29 63346
@bors retry prioritizing rollup that includes this PR
2019-08-11 19:14:57 63465
@bors retry - canceling build (Bors seems to have not noticed that it failed)

2019-08-11 09:57:57 63446
@bors retry
2019-08-10 06:14:09 63427
@bors r- retry Failed locally.
2019-08-10 05:16:04 63056
@bors retry rolled up.
2019-08-09 21:27:57 63165
@bors: retry
2019-08-09 03:28:53 61937
@bors retry rolled up.
2019-08-08 23:38:56 63162
@bors retry rolled up.
2019-08-08 21:03:03 63162
@bors retry rolled up.
2019-08-08 17:28:50 63302
@bors: retry

looks like those llvm caches needed priming
2019-08-08 17:19:19 63332
@bors retry rolled up.
2019-08-08 17:18:46 63380
@bors retry spurious network.
2019-08-07 17:01:36 63035
@bors retry r-
2019-08-06 13:37:18 62459
@bors retry
2019-08-06 12:06:13 62459
@bors retry rolled up.
2019-08-06 02:39:15 62987
@bors retry yielding to r0llup.
2019-08-06 00:24:18 62987
@bors retry yielding to r0llup.
2019-08-05 23:02:18 62987
@bors retry rolled up.
2019-08-05 22:56:38 61515
@bors retry
2019-08-03 16:26:18 63059
@bors retry

Yielded priority to https://github.com/rust-lang/rust/pull/63242
2019-08-03 16:23:28 63242
@bors retry
2019-08-03 12:20:39 62954
@bors retry rolled up.
2019-08-03 12:20:07 63234
@bors retry spurious
2019-08-02 20:54:52 63059
@bors retry rollup=never p=1

Let's isolate this PR to see if we can reproduce the error when it is tested alone.
2019-08-01 09:37:14 62507
@bors retry
2019-08-01 04:58:46 62507
@bors retry yielding to r0llup.
2019-07-31 23:50:47 62429
Something spurious, I hope...

@bors retry
2019-07-31 15:20:05 63141
It finished less than 2min after the timeout. :/

@bors retry
2019-07-30 20:50:22 62429
The timed-out build included an LLVM rebuild -- I guess we can retry?

@bors retry
2019-07-30 03:38:50 63106
@bors p=5
@bors retry rolled up.
2019-07-30 01:07:58 63106
@bors retry rolled up.
2019-07-29 23:47:15 63106
@bors retry rolled up.
2019-07-29 21:56:45 63106
@bors retry

Agent lost connection with Azure Pipelines.
2019-07-29 17:02:52 60584
@bors retry
2019-07-29 15:59:11 62507
@bors retry
2019-07-29 14:35:26 63000
@bors: retry
2019-07-29 14:31:31 62911
@bors: retry

Looks like LLVM fell out of cache
2019-07-29 14:22:22 60584
@bors retry

That... seems spurious.
2019-07-29 00:12:08 62809
@bors retry rolled up.
2019-07-28 09:11:59 63072
@bors retry r-
2019-07-28 09:09:51 63062
@bors retry
2019-07-28 05:08:53 62759
@bors retry rolled up.
2019-07-28 01:03:12 63050
@bors retry rolled up.
2019-07-27 15:41:40 63036
@bors retry rolled up
2019-07-27 11:13:29 62550
awscli download failure
@bors retry
2019-07-26 23:17:03 62086
@bors retry rolled up.
2019-07-26 21:13:25 63025
@bors retry
2019-07-26 20:55:58 62943
@bors r- retry
2019-07-26 16:57:49 63011
@bors r- retry
2019-07-26 15:11:46 62943
@bors retry
2019-07-25 21:03:09 62771
@bors retry
2019-07-25 19:02:21 62805
Thanks for the heads up, was beginning to wonder if it’s something on my side.

@bors retry
2019-07-25 18:52:46 62914
@bors: retry

* https://github.com/rust-lang/rust/issues/62967
2019-07-25 14:01:03 62966
@bors retry
2019-07-25 08:25:42 62805
@bors retry
2019-07-25 06:06:46 62944
@bors retry Yielding to https://github.com/rust-lang/rust/pull/62960#issuecomment-514909925.
2019-07-25 06:05:52 62960
@bors retry Spurious network?
2019-07-25 05:54:28 62944
@bors retry Yielding to https://github.com/rust-lang/rust/pull/62960#issuecomment-514907345.
2019-07-25 05:54:07 62960
@bors retry Spurious network.
2019-07-24 15:24:05 62805
```
aws: command not found
```

@bors retry
2019-07-24 09:57:04 62923
@bors retry
2019-07-24 05:53:31 62923
@bors retry
2019-07-24 01:51:42 62908
@bors retry
2019-07-23 23:41:29 62908
@bors retry
2019-07-23 10:56:51 62823
@bors retry
2019-07-23 10:37:21 62861
@bors retry

A VM lost network access apparently?
2019-07-22 21:11:16 62262
@bors retry try
2019-07-22 21:08:26 62262
@bors retry try
2019-07-22 17:09:05 62866
@bors retry

4hrs timeout
2019-07-22 08:56:02 62866
@bors retry
2019-07-22 06:01:43 61779
@bors retry
2019-07-21 22:21:27 62797
@bors retry
2019-07-21 17:43:28 62823
Not sure what that is... AWS complains or so?

@bors retry
2019-07-21 14:15:57 62823
@bors retry Yielding to https://github.com/rust-lang/rust/pull/62797.
2019-07-21 14:15:39 62797
@bors retry Mark says to give it another chance ;)
2019-07-21 12:36:45 62692
@bors retry Yielding to https://github.com/rust-lang/rust/pull/62797.
2019-07-21 12:36:05 62797
@bors retry Looks spurious?
2019-07-21 00:24:18 60913
@bors retry Yielding to https://github.com/rust-lang/rust/pull/62797 which is a high-risk-if-not-landed-immediately-PR.
2019-07-20 12:36:32 62736
Looks like a network issue
```
2019-07-20T12:18:08.1142326Z error: failed to download from `https://crates.io/api/v1/crates/bitflags/1.0.3/download`
2019-07-20T12:18:08.1142895Z 
2019-07-20T12:18:08.1143134Z Caused by:
2019-07-20T12:18:08.1143339Z   [35] SSL connect error (OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to crates.io:443 )
2019-07-20T12:18:08.1164594Z thread 'main' panicked at 'tests failed for https://github.com/servo/webrender', src/tools/cargotest/main.rs:88:9
```

@bors retry
2019-07-19 10:38:06 62679
```
2019-07-18T13:07:25.0878301Z D:\a\1\s\src\llvm-project\llvm\include\llvm/IR/Attributes.h(73,14):  fatal error: 'llvm/IR/Attributes.inc' file not found
```

Seems spurious?

@bors retry
2019-07-19 06:39:57 62679
2019-07-18T13:07:25.0878301Z D:\a\1\s\src\llvm-project\llvm\include\llvm/IR/Attributes.h(73,14):  fatal error: 'llvm/IR/Attributes.inc' file not found

Seems spurious?

@bors retry
2019-07-16 12:31:57 62592
@bors retry

Bors created the merge commit with the wrong base, so it failed to merge it. Why it did that is a really good question.
2019-07-16 06:51:58 62592
@bors retry

Looks spurious -- multiple jobs were cancelled due to "lost communications".
2019-07-15 16:08:09 60081
@bors retry
2019-07-15 16:08:02 62243
@bors retry
2019-07-14 10:23:00 62674
@bors r- retry

let's fix the comment
2019-07-13 09:38:55 62560
@bors retry

Spurious failure.
2019-07-12 20:48:28 61953
@bors retry
2019-07-11 20:44:44 62549
@bors: retry

azure build was killed