[17:38:06.035] New invocation is queued and will start shortly
[17:38:07.103] Starting the invocation (attempt 1)
[17:38:07.135] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/246e010dde0f0196dd702aea892e571bf30d196d"
[17:38:07.135] Popped gitiles commit info from properties and tags
[17:38:07.135] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[17:38:07.135] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[17:38:07.135] Buildbucket request:
{
"requestId": "8834191496237032176",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "246e010dde0f0196dd702aea892e571bf30d196d",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8834191496237032176"
},
{
"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"
}
}
[17:38:10.326] Scheduled build:
{
"id": "8668761432935467793",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 25578,
"createdBy": "project:chromium",
"createTime": "2026-10-05T17:38:08.564447188Z",
"updateTime": "2026-10-05T17:38:09.511006953Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "246e010dde0f0196dd702aea892e571bf30d196d",
"ref": "refs/heads/main"
}
},
"canary": true
}
[17:38:10.326] Task URL: https://cr-buildbucket-dev.appspot.com/build/8668761432935467793
[17:38:10.326] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:2:0) after 1m29s
[17:38:10.874] Received PubSub notification, asking Buildbucket for the build status
[17:38:10.895] Build status: SCHEDULED
[17:39:39.344] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:2:0)
[17:39:39.440] Build status: SCHEDULED
[17:39:39.440] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:4:0) after 2m53s
[17:42:32.458] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:4:0)
[17:42:32.478] Build status: SCHEDULED
[17:42:32.478] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:5:0) after 1m36s
[17:44:08.498] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:5:0)
[17:44:08.514] Build status: SCHEDULED
[17:44:08.514] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:6:0) after 8m2s
[17:52:10.533] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:6:0)
[17:52:10.558] Build status: SCHEDULED
[17:52:10.558] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:7:0) after 9m36s
[18:01:46.579] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:7:0)
[18:01:46.597] Build status: SCHEDULED
[18:01:46.598] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:8:0) after 6m42s
[18:08:29.216] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:8:0)
[18:08:29.302] Build status: SCHEDULED
[18:08:29.302] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:9:0) after 7m57s
[18:16:27.427] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:9:0)
[18:16:27.444] Build status: SCHEDULED
[18:16:27.444] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:10:0) after 4m17s
[18:20:44.462] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:10:0)
[18:20:44.485] Build status: SCHEDULED
[18:20:44.485] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:11:0) after 7m39s
[18:28:24.415] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:11:0)
[18:28:24.445] Build status: SCHEDULED
[18:28:24.445] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:12:0) after 3m4s
[18:31:28.464] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:12:0)
[18:31:28.485] Build status: SCHEDULED
[18:31:28.485] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:13:0) after 3m23s
[18:34:51.507] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:13:0)
[18:34:51.532] Build status: SCHEDULED
[18:34:51.532] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:14:0) after 8m41s
[18:40:04.914] Received PubSub notification, asking Buildbucket for the build status
[18:40:05.284] Build status: STARTED
[18:43:32.562] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:14:0)
[18:43:32.579] Build status: STARTED
[18:43:32.579] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:16:0) after 4m7s
[18:47:39.600] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:16:0)
[18:47:39.620] Build status: STARTED
[18:47:39.620] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:17:0) after 3m24s
[18:51:03.648] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:17:0)
[18:51:03.753] Build status: STARTED
[18:51:03.753] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:18:0) after 1m41s
[18:52:44.776] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:18:0)
[18:52:44.792] Build status: STARTED
[18:52:44.792] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:19:0) after 9m54s
[19:02:38.845] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:19:0)
[19:02:38.867] Build status: STARTED
[19:02:38.867] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:20:0) after 6m13s
[19:08:51.888] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:20:0)
[19:08:51.909] Build status: STARTED
[19:08:51.909] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:21:0) after 6m43s
[19:15:34.928] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:21:0)
[19:15:34.950] Build status: STARTED
[19:15:34.950] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:22:0) after 8m42s
[19:24:16.971] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:22:0)
[19:24:17.037] Build status: STARTED
[19:24:17.037] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:23:0) after 9m37s
[19:33:54.056] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:23:0)
[19:33:54.076] Build status: STARTED
[19:33:54.076] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:24:0) after 9m46s
[19:43:40.102] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:24:0)
[19:43:40.120] Build status: STARTED
[19:43:40.121] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:25:0) after 2m53s
[19:46:33.141] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:25:0)
[19:46:33.173] Build status: STARTED
[19:46:33.173] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:26:0) after 2m58s
[19:49:31.194] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:26:0)
[19:49:31.220] Build status: STARTED
[19:49:31.220] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:27:0) after 7m17s
[19:56:48.246] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:27:0)
[19:56:48.269] Build status: STARTED
[19:56:48.269] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:28:0) after 2m53s
[19:59:41.290] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:28:0)
[19:59:41.310] Build status: STARTED
[19:59:41.310] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:29:0) after 2m15s
[20:01:56.330] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:29:0)
[20:01:56.357] Build status: STARTED
[20:01:56.357] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:30:0) after 8m1s
[20:09:57.384] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:30:0)
[20:09:57.404] Build status: STARTED
[20:09:57.404] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:31:0) after 6m26s
[20:16:23.431] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:31:0)
[20:16:23.467] Build status: STARTED
[20:16:23.468] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:32:0) after 6m2s
[20:22:25.492] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:32:0)
[20:22:25.524] Build status: STARTED
[20:22:25.524] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:33:0) after 5m42s
[20:28:07.555] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:33:0)
[20:28:07.575] Build status: STARTED
[20:28:07.575] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:34:0) after 4m18s
[20:32:25.605] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:34:0)
[20:32:25.622] Build status: STARTED
[20:32:25.622] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:35:0) after 7m35s
[20:40:00.656] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:35:0)
[20:40:00.710] Build status: STARTED
[20:40:00.710] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:36:0) after 3m16s
[20:43:16.735] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:36:0)
[20:43:16.762] Build status: STARTED
[20:43:16.762] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:37:0) after 6m21s
[20:49:37.784] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:37:0)
[20:49:37.868] Build status: STARTED
[20:49:37.868] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:38:0) after 6m24s
[20:56:10.624] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:38:0)
[20:56:10.645] Build status: STARTED
[20:56:10.645] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:39:0) after 7m36s
[21:03:46.669] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:39:0)
[21:03:46.686] Build status: STARTED
[21:03:46.686] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:40:0) after 5m4s
[21:08:50.707] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:40:0)
[21:08:50.761] Build status: STARTED
[21:08:50.761] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:41:0) after 8m28s
[21:17:19.002] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:41:0)
[21:17:19.024] Build status: STARTED
[21:17:19.024] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:42:0) after 1m27s
[21:18:46.047] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:42:0)
[21:18:46.067] Build status: STARTED
[21:18:46.067] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:43:0) after 1m40s
[21:20:26.091] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:43:0)
[21:20:26.112] Build status: STARTED
[21:20:26.112] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:44:0) after 3m51s
[21:24:17.142] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:44:0)
[21:24:17.165] Build status: STARTED
[21:24:17.165] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:45:0) after 6m3s
[21:30:20.185] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:45:0)
[21:30:20.213] Build status: STARTED
[21:30:20.213] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8834191496237032176:46:0) after 8m10s
[21:35:12.533] Received PubSub notification, asking Buildbucket for the build status
[21:35:12.552] Build:
{
"id": "8668761432935467793",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 25578,
"createdBy": "project:chromium",
"createTime": "2026-10-05T17:38:08.564447188Z",
"startTime": "2026-10-05T18:39:54.868845726Z",
"endTime": "2026-10-05T21:35:11.861007790Z",
"updateTime": "2026-10-05T21:35:11.861007790Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "246e010dde0f0196dd702aea892e571bf30d196d",
"ref": "refs/heads/main"
}
},
"canary": true
}
[21:35:12.553] Invocation finished in 3h57m6.520517451s with status SUCCEEDED