[03:37:56.054] New invocation is queued and will start shortly
[03:37:57.112] Starting the invocation (attempt 1)
[03:37:57.137] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/9b62cfcb0495c61e755d4ab0d63683f92b2de146"
[03:37:57.137] Popped gitiles commit info from properties and tags
[03:37:57.137] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[03:37:57.138] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[03:37:57.139] Buildbucket request:
{
"requestId": "8898930588946263552",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "9b62cfcb0495c61e755d4ab0d63683f92b2de146",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8898930588946263552"
},
{
"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"
}
}
[03:37:57.967] Scheduled build:
{
"id": "8733500527079280945",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 15561,
"createdBy": "project:chromium",
"createTime": "2024-10-21T03:37:57.212323559Z",
"updateTime": "2024-10-21T03:37:57.212323559Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "9b62cfcb0495c61e755d4ab0d63683f92b2de146",
"ref": "refs/heads/main"
}
},
"canary": true
}
[03:37:57.967] Task URL: https://cr-buildbucket-dev.appspot.com/build/8733500527079280945
[03:37:57.967] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:2:0) after 1m27s
[03:37:58.585] Received PubSub notification, asking Buildbucket for the build status
[03:37:58.620] Build status: SCHEDULED
[03:39:24.984] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:2:0)
[03:39:25.016] Build status: SCHEDULED
[03:39:25.016] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:4:0) after 3m50s
[03:43:15.032] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:4:0)
[03:43:15.054] Build status: SCHEDULED
[03:43:15.054] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:5:0) after 6m2s
[03:49:17.086] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:5:0)
[03:49:17.112] Build status: SCHEDULED
[03:49:17.112] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:6:0) after 2m36s
[03:51:53.140] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:6:0)
[03:51:53.172] Build status: SCHEDULED
[03:51:53.173] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:7:0) after 4m14s
[03:56:07.193] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:7:0)
[03:56:07.221] Build status: SCHEDULED
[03:56:07.221] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:8:0) after 3m59s
[04:00:06.259] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:8:0)
[04:00:06.299] Build status: SCHEDULED
[04:00:06.299] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:9:0) after 3m2s
[04:03:08.315] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:9:0)
[04:03:08.345] Build status: SCHEDULED
[04:03:08.345] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:10:0) after 2m7s
[04:05:15.362] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:10:0)
[04:05:15.400] Build status: SCHEDULED
[04:05:15.400] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:11:0) after 5m41s
[04:10:56.416] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:11:0)
[04:10:56.464] Build status: SCHEDULED
[04:10:56.464] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:12:0) after 6m1s
[04:14:50.227] Received PubSub notification, asking Buildbucket for the build status
[04:14:50.277] Build status: STARTED
[04:16:57.898] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:12:0)
[04:16:57.922] Build status: STARTED
[04:16:57.922] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:14:0) after 2m44s
[04:19:41.942] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:14:0)
[04:19:41.975] Build status: STARTED
[04:19:41.975] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:15:0) after 1m1s
[04:20:42.996] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:15:0)
[04:20:43.041] Build status: STARTED
[04:20:43.041] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:16:0) after 8m20s
[04:29:03.060] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:16:0)
[04:29:03.100] Build status: STARTED
[04:29:03.100] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:17:0) after 8m23s
[04:37:26.116] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:17:0)
[04:37:26.174] Build status: STARTED
[04:37:26.174] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:18:0) after 7m23s
[04:44:49.755] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:18:0)
[04:44:49.816] Build status: STARTED
[04:44:49.816] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:19:0) after 1m36s
[04:46:25.830] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:19:0)
[04:46:25.863] Build status: STARTED
[04:46:25.863] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:20:0) after 4m0s
[04:50:25.878] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:20:0)
[04:50:25.904] Build status: STARTED
[04:50:25.904] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:21:0) after 7m39s
[04:58:04.926] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:21:0)
[04:58:04.952] Build status: STARTED
[04:58:04.952] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:22:0) after 2m40s
[05:00:44.971] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:22:0)
[05:00:45.007] Build status: STARTED
[05:00:45.007] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:23:0) after 8m46s
[05:09:31.377] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:23:0)
[05:09:31.409] Build status: STARTED
[05:09:31.409] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:24:0) after 9m3s
[05:18:34.429] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:24:0)
[05:18:34.475] Build status: STARTED
[05:18:34.475] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:25:0) after 3m28s
[05:22:02.496] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:25:0)
[05:22:02.533] Build status: STARTED
[05:22:02.533] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:26:0) after 1m4s
[05:23:06.553] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:26:0)
[05:23:06.590] Build status: STARTED
[05:23:06.590] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:27:0) after 6m1s
[05:29:07.605] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:27:0)
[05:29:07.628] Build status: STARTED
[05:29:07.628] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:28:0) after 2m30s
[05:31:37.676] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:28:0)
[05:31:37.713] Build status: STARTED
[05:31:37.713] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:29:0) after 5m22s
[05:36:59.730] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:29:0)
[05:36:59.786] Build status: STARTED
[05:36:59.786] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:30:0) after 6m58s
[05:43:57.804] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:30:0)
[05:43:57.837] Build status: STARTED
[05:43:57.837] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:31:0) after 4m43s
[05:48:40.854] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:31:0)
[05:48:40.906] Build status: STARTED
[05:48:40.906] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:32:0) after 8m1s
[05:56:41.923] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:32:0)
[05:56:41.956] Build status: STARTED
[05:56:41.956] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:33:0) after 3m11s
[05:59:52.971] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:33:0)
[05:59:53.018] Build status: STARTED
[05:59:53.018] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:34:0) after 4m45s
[06:04:38.034] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:34:0)
[06:04:38.063] Build status: STARTED
[06:04:38.063] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:35:0) after 3m16s
[06:07:54.082] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:35:0)
[06:07:54.106] Build status: STARTED
[06:07:54.106] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8898930588946263552:36:0) after 7m9s
[06:10:57.790] Received PubSub notification, asking Buildbucket for the build status
[06:10:57.816] Build:
{
"id": "8733500527079280945",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 15561,
"createdBy": "project:chromium",
"createTime": "2024-10-21T03:37:57.212323559Z",
"startTime": "2024-10-21T04:14:49.961424547Z",
"endTime": "2024-10-21T06:10:56.608853682Z",
"updateTime": "2024-10-21T06:10:56.608853682Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "9b62cfcb0495c61e755d4ab0d63683f92b2de146",
"ref": "refs/heads/main"
}
},
"canary": true
}
[06:10:57.816] Invocation finished in 2h33m1.768091807s with status SUCCEEDED