[19:07:37.077] New invocation is queued and will start shortly
[19:07:38.153] Starting the invocation (attempt 1)
[19:07:38.182] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/7eae909886868440c23c487f3cba773979e53bf3"
[19:07:38.182] Popped gitiles commit info from properties and tags
[19:07:38.182] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[19:07:38.183] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[19:07:38.183] Buildbucket request:
{
"requestId": "8933570736439149088",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "7eae909886868440c23c487f3cba773979e53bf3",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8933570736439149088"
},
{
"key": "scheduler_job_id",
"value": "chromium/win-rel-dev"
},
{
"key": "user_agent",
"value": "luci-scheduler-dev"
}
],
"notify": {
"pubsubTopic": "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
}
}
[19:07:39.025] Scheduled build:
{
"id": "8768140674557038001",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 2750,
"createdBy": "project:chromium",
"createTime": "2023-10-04T19:07:38.245022513Z",
"updateTime": "2023-10-04T19:07:38.245022513Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "7eae909886868440c23c487f3cba773979e53bf3",
"ref": "refs/heads/main"
}
},
"canary": true
}
[19:07:39.025] Task URL: https://cr-buildbucket-dev.appspot.com/build/8768140674557038001
[19:07:39.025] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:2:0) after 3m9s
[19:08:15.687] Received PubSub notification, asking Buildbucket for the build status
[19:08:15.713] Build status: SCHEDULED
[19:10:48.049] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:2:0)
[19:10:48.073] Build status: SCHEDULED
[19:10:48.073] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:4:0) after 6m41s
[19:17:29.139] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:4:0)
[19:17:29.157] Build status: SCHEDULED
[19:17:29.157] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:5:0) after 2m9s
[19:19:38.178] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:5:0)
[19:19:38.202] Build status: SCHEDULED
[19:19:38.202] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:6:0) after 3m2s
[19:22:40.231] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:6:0)
[19:22:40.253] Build status: SCHEDULED
[19:22:40.253] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:7:0) after 2m35s
[19:25:15.288] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:7:0)
[19:25:15.316] Build status: SCHEDULED
[19:25:15.316] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:8:0) after 6m25s
[19:31:40.401] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:8:0)
[19:31:40.427] Build status: SCHEDULED
[19:31:40.427] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:9:0) after 2m29s
[19:33:19.544] Received PubSub notification, asking Buildbucket for the build status
[19:33:19.563] Build status: STARTED
[19:34:09.976] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:9:0)
[19:34:10.004] Build status: STARTED
[19:34:10.004] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:11:0) after 3m48s
[19:37:58.033] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:11:0)
[19:37:58.082] Build status: STARTED
[19:37:58.082] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:12:0) after 2m45s
[19:40:43.105] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:12:0)
[19:40:43.138] Build status: STARTED
[19:40:43.138] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:13:0) after 9m17s
[19:50:00.158] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:13:0)
[19:50:00.408] Build status: STARTED
[19:50:00.408] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:14:0) after 1m7s
[19:51:07.435] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:14:0)
[19:51:07.479] Build status: STARTED
[19:51:07.479] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:15:0) after 5m14s
[19:56:21.511] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:15:0)
[19:56:21.546] Build status: STARTED
[19:56:21.546] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:16:0) after 3m43s
[20:00:04.581] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:16:0)
[20:00:04.609] Build status: STARTED
[20:00:04.609] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:17:0) after 9m39s
[20:09:43.628] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:17:0)
[20:09:43.645] Build status: STARTED
[20:09:43.645] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:18:0) after 4m45s
[20:14:28.668] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:18:0)
[20:14:28.718] Build status: STARTED
[20:14:28.718] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:19:0) after 8m12s
[20:22:40.736] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:19:0)
[20:22:40.772] Build status: STARTED
[20:22:40.772] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:20:0) after 9m2s
[20:31:42.802] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:20:0)
[20:31:42.829] Build status: STARTED
[20:31:42.829] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:21:0) after 3m32s
[20:35:14.849] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:21:0)
[20:35:14.874] Build status: STARTED
[20:35:14.874] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:22:0) after 3m14s
[20:38:28.897] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:22:0)
[20:38:28.917] Build status: STARTED
[20:38:28.917] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:23:0) after 4m29s
[20:42:57.944] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:23:0)
[20:42:57.969] Build status: STARTED
[20:42:57.969] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:24:0) after 1m4s
[20:44:01.997] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:24:0)
[20:44:02.026] Build status: STARTED
[20:44:02.026] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:25:0) after 4m45s
[20:48:47.051] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:25:0)
[20:48:47.085] Build status: STARTED
[20:48:47.085] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:26:0) after 6m20s
[20:55:07.106] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:26:0)
[20:55:07.138] Build status: STARTED
[20:55:07.138] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:27:0) after 2m51s
[20:57:58.157] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:27:0)
[20:57:58.188] Build status: STARTED
[20:57:58.188] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:28:0) after 4m43s
[21:02:41.241] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:28:0)
[21:02:41.305] Build status: STARTED
[21:02:41.305] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:29:0) after 5m13s
[21:07:54.330] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:29:0)
[21:07:54.365] Build status: STARTED
[21:07:54.365] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:30:0) after 3m5s
[21:10:59.385] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:30:0)
[21:10:59.409] Build status: STARTED
[21:10:59.409] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8933570736439149088:31:0) after 7m16s
[21:14:14.818] Received PubSub notification, asking Buildbucket for the build status
[21:14:14.843] Build:
{
"id": "8768140674557038001",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 2750,
"createdBy": "project:chromium",
"createTime": "2023-10-04T19:07:38.245022513Z",
"startTime": "2023-10-04T19:33:18.956546Z",
"endTime": "2023-10-04T21:13:04.539614052Z",
"updateTime": "2023-10-04T21:13:04.539614052Z",
"status": "FAILURE",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "7eae909886868440c23c487f3cba773979e53bf3",
"ref": "refs/heads/main"
}
},
"canary": true
}
[21:14:14.843] Invocation finished in 2h6m37.775722267s with status FAILED