[01:28:22.051] New invocation is queued and will start shortly
[01:28:23.170] Starting the invocation (attempt 1)
[01:28:23.219] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/6f54a0050a20bb28679c94622b7d18e72599ae17"
[01:28:23.219] Popped gitiles commit info from properties and tags
[01:28:23.219] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[01:28:23.220] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[01:28:23.220] Buildbucket request:
{
"requestId": "8857988911769054896",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "6f54a0050a20bb28679c94622b7d18e72599ae17",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8857988911769054896"
},
{
"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"
}
}
[01:28:24.205] Scheduled build:
{
"id": "8692558849813964865",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 21249,
"createdBy": "project:chromium",
"createTime": "2026-01-16T01:28:23.290865745Z",
"updateTime": "2026-01-16T01:28:23.290865745Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "6f54a0050a20bb28679c94622b7d18e72599ae17",
"ref": "refs/heads/main"
}
},
"canary": true
}
[01:28:24.205] Task URL: https://cr-buildbucket-dev.appspot.com/build/8692558849813964865
[01:28:24.205] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:2:0) after 1m54s
[01:28:37.644] Received PubSub notification, asking Buildbucket for the build status
[01:28:37.665] Build status: SCHEDULED
[01:30:18.223] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:2:0)
[01:30:18.244] Build status: SCHEDULED
[01:30:18.244] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:4:0) after 1m51s
[01:32:09.266] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:4:0)
[01:32:09.346] Build status: SCHEDULED
[01:32:09.346] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:5:0) after 9m13s
[01:37:12.007] Received PubSub notification, asking Buildbucket for the build status
[01:37:12.026] Build status: STARTED
[01:41:22.372] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:5:0)
[01:41:22.392] Build status: STARTED
[01:41:22.392] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:7:0) after 9m22s
[01:50:44.410] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:7:0)
[01:50:44.427] Build status: STARTED
[01:50:44.427] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:8:0) after 9m22s
[02:00:06.447] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:8:0)
[02:00:06.509] Build status: STARTED
[02:00:06.509] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:9:0) after 5m40s
[02:05:46.528] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:9:0)
[02:05:46.547] Build status: STARTED
[02:05:46.547] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:10:0) after 2m59s
[02:08:45.612] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:10:0)
[02:08:45.630] Build status: STARTED
[02:08:45.630] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:11:0) after 1m31s
[02:10:16.654] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:11:0)
[02:10:16.678] Build status: STARTED
[02:10:16.678] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:12:0) after 9m7s
[02:19:23.739] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:12:0)
[02:19:23.762] Build status: STARTED
[02:19:23.763] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:13:0) after 3m36s
[02:22:59.787] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:13:0)
[02:22:59.816] Build status: STARTED
[02:22:59.816] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:14:0) after 5m4s
[02:28:03.837] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:14:0)
[02:28:03.890] Build status: STARTED
[02:28:03.890] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:15:0) after 8m9s
[02:36:12.911] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:15:0)
[02:36:12.931] Build status: STARTED
[02:36:12.931] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:16:0) after 8m13s
[02:44:25.953] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:16:0)
[02:44:25.987] Build status: STARTED
[02:44:25.987] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:17:0) after 6m37s
[02:51:03.007] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:17:0)
[02:51:03.029] Build status: STARTED
[02:51:03.029] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:18:0) after 7m3s
[02:58:06.051] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:18:0)
[02:58:06.066] Build status: STARTED
[02:58:06.066] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:19:0) after 6m52s
[03:04:58.087] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:19:0)
[03:04:58.117] Build status: STARTED
[03:04:58.117] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:20:0) after 5m39s
[03:10:37.137] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:20:0)
[03:10:37.155] Build status: STARTED
[03:10:37.155] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:21:0) after 1m56s
[03:12:33.176] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:21:0)
[03:12:33.193] Build status: STARTED
[03:12:33.193] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:22:0) after 2m46s
[03:15:19.222] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:22:0)
[03:15:19.240] Build status: STARTED
[03:15:19.240] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:23:0) after 4m23s
[03:19:42.266] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:23:0)
[03:19:42.285] Build status: STARTED
[03:19:42.285] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:24:0) after 2m33s
[03:22:16.060] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:24:0)
[03:22:16.085] Build status: STARTED
[03:22:16.085] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:25:0) after 7m12s
[03:29:28.107] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:25:0)
[03:29:28.140] Build status: STARTED
[03:29:28.140] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:26:0) after 9m16s
[03:38:44.164] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:26:0)
[03:38:44.182] Build status: STARTED
[03:38:44.182] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:27:0) after 1m27s
[03:40:11.919] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:27:0)
[03:40:11.942] Build status: STARTED
[03:40:11.942] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:28:0) after 5m58s
[03:46:09.962] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:28:0)
[03:46:09.997] Build status: STARTED
[03:46:09.997] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:29:0) after 7m41s
[03:53:51.015] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:29:0)
[03:53:51.036] Build status: STARTED
[03:53:51.036] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:30:0) after 7m27s
[04:01:18.055] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:30:0)
[04:01:18.233] Build status: STARTED
[04:01:18.233] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857988911769054896:31:0) after 4m7s
[04:01:39.028] Received PubSub notification, asking Buildbucket for the build status
[04:01:39.052] Build:
{
"id": "8692558849813964865",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 21249,
"createdBy": "project:chromium",
"createTime": "2026-01-16T01:28:23.290865745Z",
"startTime": "2026-01-16T01:37:11.836931158Z",
"endTime": "2026-01-16T04:01:38.743214765Z",
"updateTime": "2026-01-16T04:01:38.743214765Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "6f54a0050a20bb28679c94622b7d18e72599ae17",
"ref": "refs/heads/main"
}
},
"canary": true
}
[04:01:39.052] Invocation finished in 2h33m17.00982992s with status SUCCEEDED