[05:13:32.042] New invocation is queued and will start shortly
[05:13:33.092] Starting the invocation (attempt 1)
[05:13:33.112] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/1d867aaf5c2173b8fee553e642af6dd6f650f223"
[05:13:33.112] Popped gitiles commit info from properties and tags
[05:13:33.113] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[05:13:33.113] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[05:13:33.113] Buildbucket request:
{
"requestId": "8846921915610914016",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1d867aaf5c2173b8fee553e642af6dd6f650f223",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8846921915610914016"
},
{
"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"
}
}
[05:13:34.170] Scheduled build:
{
"id": "8681491853722218481",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 37774,
"createdBy": "project:chromium",
"createTime": "2026-05-18T05:13:33.223607228Z",
"updateTime": "2026-05-18T05:13:33.223607228Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1d867aaf5c2173b8fee553e642af6dd6f650f223",
"ref": "refs/heads/main"
}
},
"canary": true
}
[05:13:34.170] Task URL: https://cr-buildbucket-dev.appspot.com/build/8681491853722218481
[05:13:34.170] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:2:0) after 5m9s
[05:13:35.142] Received PubSub notification, asking Buildbucket for the build status
[05:13:35.160] Build status: SCHEDULED
[05:18:43.187] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:2:0)
[05:18:43.209] Build status: SCHEDULED
[05:18:43.209] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:4:0) after 1m56s
[05:20:39.223] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:4:0)
[05:20:39.242] Build status: SCHEDULED
[05:20:39.242] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:5:0) after 8m19s
[05:23:22.235] Received PubSub notification, asking Buildbucket for the build status
[05:23:22.262] Build status: STARTED
[05:28:58.254] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:5:0)
[05:28:58.380] Build status: STARTED
[05:28:58.380] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:7:0) after 5m47s
[05:34:45.394] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:7:0)
[05:34:45.421] Build status: STARTED
[05:34:45.421] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:8:0) after 4m32s
[05:39:17.434] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:8:0)
[05:39:17.466] Build status: STARTED
[05:39:17.466] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:9:0) after 7m47s
[05:47:04.480] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:9:0)
[05:47:04.503] Build status: STARTED
[05:47:04.503] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:10:0) after 8m55s
[05:55:59.520] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:10:0)
[05:55:59.544] Build status: STARTED
[05:55:59.544] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:11:0) after 4m5s
[06:00:04.558] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:11:0)
[06:00:04.582] Build status: STARTED
[06:00:04.582] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:12:0) after 1m24s
[06:01:28.599] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:12:0)
[06:01:28.618] Build status: STARTED
[06:01:28.618] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:13:0) after 2m39s
[06:04:07.645] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:13:0)
[06:04:07.672] Build status: STARTED
[06:04:07.672] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:14:0) after 2m31s
[06:06:38.686] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:14:0)
[06:06:38.716] Build status: STARTED
[06:06:38.717] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:15:0) after 4m22s
[06:11:00.729] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:15:0)
[06:11:00.743] Build status: STARTED
[06:11:00.743] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:16:0) after 6m20s
[06:17:20.755] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:16:0)
[06:17:20.772] Build status: STARTED
[06:17:20.772] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:17:0) after 3m0s
[06:20:20.792] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:17:0)
[06:20:20.811] Build status: STARTED
[06:20:20.811] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:18:0) after 5m17s
[06:25:37.830] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:18:0)
[06:25:37.849] Build status: STARTED
[06:25:37.849] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:19:0) after 2m58s
[06:28:35.864] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:19:0)
[06:28:35.885] Build status: STARTED
[06:28:35.886] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:20:0) after 7m47s
[06:36:22.897] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:20:0)
[06:36:22.926] Build status: STARTED
[06:36:22.926] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:21:0) after 4m48s
[06:41:10.939] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:21:0)
[06:41:10.963] Build status: STARTED
[06:41:10.963] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8846921915610914016:22:0) after 3m49s
[06:42:19.769] Received PubSub notification, asking Buildbucket for the build status
[06:42:19.788] Build:
{
"id": "8681491853722218481",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 37774,
"createdBy": "project:chromium",
"createTime": "2026-05-18T05:13:33.223607228Z",
"startTime": "2026-05-18T05:23:21.367811613Z",
"endTime": "2026-05-18T06:42:19.487072546Z",
"updateTime": "2026-05-18T06:42:19.487072546Z",
"status": "INFRA_FAILURE",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1d867aaf5c2173b8fee553e642af6dd6f650f223",
"ref": "refs/heads/main"
}
},
"canary": true
}
[06:42:19.788] Invocation finished in 1h28m47.749688032s with status FAILED