[18:17:38.038] New invocation is queued and will start shortly
[18:17:39.097] Starting the invocation (attempt 1)
[18:17:39.123] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/57c4fbfe688a2b04439f5001f0b84fc11517ef40"
[18:17:39.123] Popped gitiles commit info from properties and tags
[18:17:39.123] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[18:17:39.123] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[18:17:39.123] Buildbucket request:
{
"requestId": "8843339302620629312",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "57c4fbfe688a2b04439f5001f0b84fc11517ef40",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8843339302620629312"
},
{
"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"
}
}
[18:17:40.221] Scheduled build:
{
"id": "8677909240750140305",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 24325,
"createdBy": "project:chromium",
"createTime": "2026-06-26T18:17:39.200302852Z",
"updateTime": "2026-06-26T18:17:39.200302852Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "57c4fbfe688a2b04439f5001f0b84fc11517ef40",
"ref": "refs/heads/main"
}
}
}
[18:17:40.221] Task URL: https://cr-buildbucket-dev.appspot.com/build/8677909240750140305
[18:17:40.222] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:2:0) after 4m27s
[18:17:41.223] Received PubSub notification, asking Buildbucket for the build status
[18:17:41.253] Build status: SCHEDULED
[18:22:07.239] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:2:0)
[18:22:07.257] Build status: SCHEDULED
[18:22:07.257] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:4:0) after 3m40s
[18:25:47.277] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:4:0)
[18:25:47.299] Build status: SCHEDULED
[18:25:47.299] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:5:0) after 3m29s
[18:29:16.326] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:5:0)
[18:29:16.343] Build status: SCHEDULED
[18:29:16.343] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:6:0) after 3m47s
[18:31:04.479] Received PubSub notification, asking Buildbucket for the build status
[18:31:04.502] Build status: STARTED
[18:33:03.359] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:6:0)
[18:33:03.377] Build status: STARTED
[18:33:03.377] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:8:0) after 9m50s
[18:42:53.394] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:8:0)
[18:42:53.412] Build status: STARTED
[18:42:53.412] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:9:0) after 6m24s
[18:49:17.431] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:9:0)
[18:49:17.452] Build status: STARTED
[18:49:17.452] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:10:0) after 2m49s
[18:52:06.497] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:10:0)
[18:52:06.516] Build status: STARTED
[18:52:06.516] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:11:0) after 8m6s
[19:00:12.565] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:11:0)
[19:00:12.613] Build status: STARTED
[19:00:12.613] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:12:0) after 3m7s
[19:03:19.631] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:12:0)
[19:03:19.654] Build status: STARTED
[19:03:19.654] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:13:0) after 7m58s
[19:11:17.671] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:13:0)
[19:11:17.695] Build status: STARTED
[19:11:17.695] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:14:0) after 7m3s
[19:18:20.712] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:14:0)
[19:18:20.804] Build status: STARTED
[19:18:20.804] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:15:0) after 9m29s
[19:27:49.824] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:15:0)
[19:27:49.844] Build status: STARTED
[19:27:49.845] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:16:0) after 4m27s
[19:32:16.862] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:16:0)
[19:32:16.880] Build status: STARTED
[19:32:16.880] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:17:0) after 7m30s
[19:39:46.900] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:17:0)
[19:39:46.919] Build status: STARTED
[19:39:46.919] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:18:0) after 3m1s
[19:42:47.941] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:18:0)
[19:42:47.976] Build status: STARTED
[19:42:47.976] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:19:0) after 4m12s
[19:46:59.993] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:19:0)
[19:47:00.017] Build status: STARTED
[19:47:00.017] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:20:0) after 1m9s
[19:48:09.041] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:20:0)
[19:48:09.073] Build status: STARTED
[19:48:09.074] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:21:0) after 7m53s
[19:56:02.093] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:21:0)
[19:56:02.295] Build status: STARTED
[19:56:02.295] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:22:0) after 8m51s
[20:04:53.314] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:22:0)
[20:04:53.335] Build status: STARTED
[20:04:53.335] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:23:0) after 9m42s
[20:14:35.354] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:23:0)
[20:14:35.381] Build status: STARTED
[20:14:35.382] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:24:0) after 4m53s
[20:19:28.407] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:24:0)
[20:19:28.422] Build status: STARTED
[20:19:28.422] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:25:0) after 5m41s
[20:25:09.442] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:25:0)
[20:25:09.470] Build status: STARTED
[20:25:09.470] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:26:0) after 8m56s
[20:34:05.490] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:26:0)
[20:34:05.546] Build status: STARTED
[20:34:05.546] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:27:0) after 1m22s
[20:35:27.564] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:27:0)
[20:35:27.599] Build status: STARTED
[20:35:27.599] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:28:0) after 6m48s
[20:42:15.577] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:28:0)
[20:42:15.609] Build status: STARTED
[20:42:15.609] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:29:0) after 3m1s
[20:45:16.626] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:29:0)
[20:45:16.650] Build status: STARTED
[20:45:16.650] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:30:0) after 2m57s
[20:48:13.672] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:30:0)
[20:48:13.728] Build status: STARTED
[20:48:13.728] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8843339302620629312:31:0) after 8m44s
[20:51:13.494] Received PubSub notification, asking Buildbucket for the build status
[20:51:13.513] Build:
{
"id": "8677909240750140305",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 24325,
"createdBy": "project:chromium",
"createTime": "2026-06-26T18:17:39.200302852Z",
"startTime": "2026-06-26T18:31:03.789602647Z",
"endTime": "2026-06-26T20:51:12.431102365Z",
"updateTime": "2026-06-26T20:51:12.431102365Z",
"status": "FAILURE",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "57c4fbfe688a2b04439f5001f0b84fc11517ef40",
"ref": "refs/heads/main"
}
}
}
[20:51:13.513] Invocation finished in 2h33m35.480045959s with status FAILED