[09:24:49.053] New invocation is queued and will start shortly
[09:24:50.106] Starting the invocation (attempt 1)
[09:24:50.130] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/d30ab9187bbff21d52da86afd22b1841ca0c828a"
[09:24:50.130] Popped gitiles commit info from properties and tags
[09:24:50.130] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[09:24:50.135] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[09:24:50.135] Buildbucket request:
{
"requestId": "8892566977289050528",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "d30ab9187bbff21d52da86afd22b1841ca0c828a",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8892566977289050528"
},
{
"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"
}
}
[09:24:51.049] Scheduled build:
{
"id": "8727136915449125985",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 21065,
"createdBy": "project:chromium",
"createTime": "2024-12-30T09:24:50.183417936Z",
"updateTime": "2024-12-30T09:24:50.183417936Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "d30ab9187bbff21d52da86afd22b1841ca0c828a",
"ref": "refs/heads/main"
}
},
"canary": true
}
[09:24:51.049] Task URL: https://cr-buildbucket-dev.appspot.com/build/8727136915449125985
[09:24:51.049] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:2:0) after 1m5s
[09:24:52.119] Received PubSub notification, asking Buildbucket for the build status
[09:24:52.140] Build status: SCHEDULED
[09:25:56.068] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:2:0)
[09:25:56.087] Build status: SCHEDULED
[09:25:56.087] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:4:0) after 3m58s
[09:29:54.109] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:4:0)
[09:29:54.127] Build status: SCHEDULED
[09:29:54.127] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:5:0) after 3m42s
[09:33:36.138] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:5:0)
[09:33:36.156] Build status: SCHEDULED
[09:33:36.156] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:6:0) after 1m19s
[09:34:55.168] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:6:0)
[09:34:55.239] Build status: SCHEDULED
[09:34:55.239] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:7:0) after 3m55s
[09:35:25.165] Received PubSub notification, asking Buildbucket for the build status
[09:35:25.184] Build status: STARTED
[09:38:50.304] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:7:0)
[09:38:50.331] Build status: STARTED
[09:38:50.331] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:9:0) after 3m55s
[09:42:45.350] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:9:0)
[09:42:45.373] Build status: STARTED
[09:42:45.373] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:10:0) after 7m19s
[09:50:04.393] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:10:0)
[09:50:04.423] Build status: STARTED
[09:50:04.423] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:11:0) after 5m38s
[09:55:42.433] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:11:0)
[09:55:42.451] Build status: STARTED
[09:55:42.451] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:12:0) after 3m27s
[09:59:09.468] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:12:0)
[09:59:09.497] Build status: STARTED
[09:59:09.497] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:13:0) after 4m6s
[10:03:15.513] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:13:0)
[10:03:15.542] Build status: STARTED
[10:03:15.542] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:14:0) after 1m3s
[10:04:18.558] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:14:0)
[10:04:18.582] Build status: STARTED
[10:04:18.582] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:15:0) after 9m11s
[10:13:29.604] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:15:0)
[10:13:29.639] Build status: STARTED
[10:13:29.639] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:16:0) after 3m21s
[10:16:50.656] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:16:0)
[10:16:50.702] Build status: STARTED
[10:16:50.702] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:17:0) after 7m19s
[10:24:09.715] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:17:0)
[10:24:09.733] Build status: STARTED
[10:24:09.733] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:18:0) after 4m27s
[10:28:36.747] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:18:0)
[10:28:36.780] Build status: STARTED
[10:28:36.780] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:19:0) after 3m46s
[10:32:22.798] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:19:0)
[10:32:22.846] Build status: STARTED
[10:32:22.846] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:20:0) after 3m33s
[10:35:55.858] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:20:0)
[10:35:55.888] Build status: STARTED
[10:35:55.888] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:21:0) after 8m13s
[10:44:08.911] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:21:0)
[10:44:08.966] Build status: STARTED
[10:44:08.966] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:22:0) after 1m29s
[10:45:37.982] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:22:0)
[10:45:38.006] Build status: STARTED
[10:45:38.006] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:23:0) after 4m12s
[10:49:50.021] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:23:0)
[10:49:50.045] Build status: STARTED
[10:49:50.045] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:24:0) after 3m41s
[10:53:31.059] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:24:0)
[10:53:31.078] Build status: STARTED
[10:53:31.078] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:25:0) after 7m53s
[11:01:24.091] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:25:0)
[11:01:24.107] Build status: STARTED
[11:01:24.107] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:26:0) after 6m38s
[11:08:02.136] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:26:0)
[11:08:02.163] Build status: STARTED
[11:08:02.163] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:27:0) after 8m27s
[11:16:29.229] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:27:0)
[11:16:29.256] Build status: STARTED
[11:16:29.257] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:28:0) after 9m35s
[11:26:04.272] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:28:0)
[11:26:04.306] Build status: STARTED
[11:26:04.306] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8892566977289050528:29:0) after 9m46s
[11:28:16.102] Received PubSub notification, asking Buildbucket for the build status
[11:28:16.130] Build:
{
"id": "8727136915449125985",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 21065,
"createdBy": "project:chromium",
"createTime": "2024-12-30T09:24:50.183417936Z",
"startTime": "2024-12-30T09:35:24.735386021Z",
"endTime": "2024-12-30T11:28:15.765371318Z",
"updateTime": "2024-12-30T11:28:15.765371318Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "d30ab9187bbff21d52da86afd22b1841ca0c828a",
"ref": "refs/heads/main"
}
},
"canary": true
}
[11:28:16.130] Invocation finished in 2h3m27.085390965s with status SUCCEEDED