[17:35:18.168] New invocation is queued and will start shortly
[17:35:19.283] Starting the invocation (attempt 1)
[17:35:19.325] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/6479de38d574bab4a1d2f3c7f589bfd9732d7a2a"
[17:35:19.325] Popped gitiles commit info from properties and tags
[17:35:19.325] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[17:35:19.325] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[17:35:19.325] Buildbucket request:
{
"requestId": "8926509981028922160",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "6479de38d574bab4a1d2f3c7f589bfd9732d7a2a",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8926509981028922160"
},
{
"key": "scheduler_job_id",
"value": "chromium/win-local-ssd-rel-dev"
},
{
"key": "user_agent",
"value": "luci-scheduler-dev"
}
],
"notify": {
"pubsubTopic": "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
}
}
[17:35:24.344] Scheduled build:
{
"id": "8761079919032313297",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 6099,
"createdBy": "project:chromium",
"createTime": "2023-12-21T17:35:19.444443312Z",
"updateTime": "2023-12-21T17:35:19.444443312Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "6479de38d574bab4a1d2f3c7f589bfd9732d7a2a",
"ref": "refs/heads/main"
}
},
"canary": true
}
[17:35:24.344] Task URL: https://cr-buildbucket-dev.appspot.com/build/8761079919032313297
[17:35:24.344] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:2:0) after 6m20s
[17:35:25.218] Received PubSub notification, asking Buildbucket for the build status
[17:35:25.239] Build status: SCHEDULED
[17:41:44.393] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:2:0)
[17:41:44.461] Build status: SCHEDULED
[17:41:44.461] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:4:0) after 8m45s
[17:50:29.476] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:4:0)
[17:50:29.535] Build status: SCHEDULED
[17:50:29.535] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:5:0) after 1m55s
[17:52:24.563] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:5:0)
[17:52:24.623] Build status: SCHEDULED
[17:52:24.623] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:6:0) after 2m26s
[17:54:50.643] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:6:0)
[17:54:50.757] Build status: SCHEDULED
[17:54:50.757] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:7:0) after 2m59s
[17:57:49.780] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:7:0)
[17:57:49.826] Build status: SCHEDULED
[17:57:49.826] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:8:0) after 3m10s
[18:00:59.848] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:8:0)
[18:00:59.905] Build status: SCHEDULED
[18:00:59.905] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:9:0) after 1m19s
[18:02:18.979] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:9:0)
[18:02:19.046] Build status: SCHEDULED
[18:02:19.046] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:10:0) after 1m41s
[18:04:00.072] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:10:0)
[18:04:00.114] Build status: SCHEDULED
[18:04:00.114] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:11:0) after 8m41s
[18:12:41.724] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:11:0)
[18:12:41.749] Build status: SCHEDULED
[18:12:41.749] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:12:0) after 8m2s
[18:20:43.781] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:12:0)
[18:20:43.836] Build status: SCHEDULED
[18:20:43.836] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:13:0) after 1m58s
[18:22:41.967] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:13:0)
[18:22:42.003] Build status: SCHEDULED
[18:22:42.003] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:14:0) after 8m33s
[18:24:01.153] Received PubSub notification, asking Buildbucket for the build status
[18:24:01.183] Build status: STARTED
[18:31:15.055] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:14:0)
[18:31:15.163] Build status: STARTED
[18:31:15.163] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:16:0) after 2m39s
[18:33:54.188] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:16:0)
[18:33:54.236] Build status: STARTED
[18:33:54.236] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:17:0) after 8m26s
[18:42:20.253] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:17:0)
[18:42:20.352] Build status: STARTED
[18:42:20.352] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:18:0) after 3m56s
[18:46:16.406] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:18:0)
[18:46:16.497] Build status: STARTED
[18:46:16.497] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:19:0) after 3m45s
[18:50:01.519] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:19:0)
[18:50:01.570] Build status: STARTED
[18:50:01.570] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:20:0) after 9m53s
[18:59:54.591] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:20:0)
[18:59:54.640] Build status: STARTED
[18:59:54.640] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:21:0) after 8m53s
[19:08:47.660] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:21:0)
[19:08:47.723] Build status: STARTED
[19:08:47.723] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:22:0) after 2m41s
[19:11:28.756] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:22:0)
[19:11:28.821] Build status: STARTED
[19:11:28.821] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:23:0) after 9m59s
[19:21:27.839] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:23:0)
[19:21:27.912] Build status: STARTED
[19:21:27.912] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:24:0) after 4m6s
[19:25:33.947] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:24:0)
[19:25:34.027] Build status: STARTED
[19:25:34.027] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:25:0) after 5m17s
[19:30:51.960] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:25:0)
[19:30:52.001] Build status: STARTED
[19:30:52.001] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:26:0) after 2m32s
[19:33:24.024] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:26:0)
[19:33:24.095] Build status: STARTED
[19:33:24.095] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:27:0) after 2m21s
[19:35:45.112] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:27:0)
[19:35:45.156] Build status: STARTED
[19:35:45.156] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:28:0) after 5m17s
[19:41:02.182] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:28:0)
[19:41:02.245] Build status: STARTED
[19:41:02.246] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:29:0) after 7m38s
[19:48:40.273] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:29:0)
[19:48:40.326] Build status: STARTED
[19:48:40.326] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:30:0) after 8m31s
[19:57:11.680] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:30:0)
[19:57:11.716] Build status: STARTED
[19:57:11.716] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:31:0) after 5m53s
[20:03:04.742] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:31:0)
[20:03:04.833] Build status: STARTED
[20:03:04.833] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:32:0) after 4m10s
[20:07:14.875] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:32:0)
[20:07:14.942] Build status: STARTED
[20:07:14.942] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:33:0) after 8m54s
[20:16:09.047] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:33:0)
[20:16:09.076] Build status: STARTED
[20:16:09.076] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:34:0) after 1m33s
[20:17:42.121] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:34:0)
[20:17:42.162] Build status: STARTED
[20:17:42.162] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:35:0) after 4m25s
[20:22:07.185] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:35:0)
[20:22:07.304] Build status: STARTED
[20:22:07.304] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8926509981028922160:36:0) after 7m17s
[20:25:19.830] Received PubSub notification, asking Buildbucket for the build status
[20:25:19.864] Build:
{
"id": "8761079919032313297",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 6099,
"createdBy": "project:chromium",
"createTime": "2023-12-21T17:35:19.444443312Z",
"startTime": "2023-12-21T18:23:59.401180261Z",
"endTime": "2023-12-21T20:25:18.430390032Z",
"updateTime": "2023-12-21T20:25:18.430390032Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "6479de38d574bab4a1d2f3c7f589bfd9732d7a2a",
"ref": "refs/heads/main"
}
},
"canary": true
}
[20:25:19.864] Invocation finished in 2h50m1.70796335s with status SUCCEEDED