[18:45:16.049] New invocation is queued and will start shortly
[18:45:17.110] Starting the invocation (attempt 1)
[18:45:17.175] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/f4e4d1f36ed4c89f41f345580570034f1219860b"
[18:45:17.175] Popped gitiles commit info from properties and tags
[18:45:17.175] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[18:45:17.175] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[18:45:17.176] Buildbucket request:
{
"requestId": "8842793982269688560",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "f4e4d1f36ed4c89f41f345580570034f1219860b",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8842793982269688560"
},
{
"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:45:18.653] Scheduled build:
{
"id": "8677363920361650705",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 24386,
"createdBy": "project:chromium",
"createTime": "2026-07-02T18:45:17.248818138Z",
"updateTime": "2026-07-02T18:45:17.248818138Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "f4e4d1f36ed4c89f41f345580570034f1219860b",
"ref": "refs/heads/main"
}
},
"canary": true
}
[18:45:18.653] Task URL: https://cr-buildbucket-dev.appspot.com/build/8677363920361650705
[18:45:18.653] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:2:0) after 4m2s
[18:45:19.173] Received PubSub notification, asking Buildbucket for the build status
[18:45:19.191] Build status: SCHEDULED
[18:49:20.674] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:2:0)
[18:49:20.695] Build status: SCHEDULED
[18:49:20.695] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:4:0) after 6m17s
[18:55:37.714] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:4:0)
[18:55:37.743] Build status: SCHEDULED
[18:55:37.743] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:5:0) after 8m52s
[19:04:29.758] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:5:0)
[19:04:29.793] Build status: SCHEDULED
[19:04:29.793] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:6:0) after 9m6s
[19:12:26.839] Received PubSub notification, asking Buildbucket for the build status
[19:12:26.877] Build status: STARTED
[19:13:35.817] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:6:0)
[19:13:35.849] Build status: STARTED
[19:13:35.849] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:8:0) after 6m26s
[19:20:01.878] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:8:0)
[19:20:01.896] Build status: STARTED
[19:20:01.896] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:9:0) after 1m5s
[19:21:06.913] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:9:0)
[19:21:06.933] Build status: STARTED
[19:21:06.933] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:10:0) after 6m42s
[19:27:48.963] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:10:0)
[19:27:49.005] Build status: STARTED
[19:27:49.005] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:11:0) after 4m9s
[19:31:58.024] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:11:0)
[19:31:58.046] Build status: STARTED
[19:31:58.046] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:12:0) after 2m39s
[19:34:37.066] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:12:0)
[19:34:37.093] Build status: STARTED
[19:34:37.093] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:13:0) after 3m8s
[19:37:45.114] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:13:0)
[19:37:45.133] Build status: STARTED
[19:37:45.133] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:14:0) after 8m24s
[19:46:09.158] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:14:0)
[19:46:09.186] Build status: STARTED
[19:46:09.186] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:15:0) after 9m13s
[19:55:22.205] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:15:0)
[19:55:22.239] Build status: STARTED
[19:55:22.239] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:16:0) after 3m43s
[19:59:05.256] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:16:0)
[19:59:05.272] Build status: STARTED
[19:59:05.272] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:17:0) after 8m56s
[20:08:01.290] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:17:0)
[20:08:01.314] Build status: STARTED
[20:08:01.314] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:18:0) after 9m25s
[20:17:26.333] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:18:0)
[20:17:26.363] Build status: STARTED
[20:17:26.363] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:19:0) after 7m33s
[20:24:59.383] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:19:0)
[20:24:59.398] Build status: STARTED
[20:24:59.398] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:20:0) after 9m47s
[20:34:46.417] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:20:0)
[20:34:46.436] Build status: STARTED
[20:34:46.436] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:21:0) after 7m26s
[20:42:12.459] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:21:0)
[20:42:12.485] Build status: STARTED
[20:42:12.485] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:22:0) after 2m46s
[20:44:58.504] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:22:0)
[20:44:58.547] Build status: STARTED
[20:44:58.547] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:23:0) after 7m0s
[20:51:58.564] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:23:0)
[20:51:58.588] Build status: STARTED
[20:51:58.588] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:24:0) after 5m10s
[20:57:08.604] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:24:0)
[20:57:08.623] Build status: STARTED
[20:57:08.623] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:25:0) after 2m16s
[20:59:24.640] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:25:0)
[20:59:24.662] Build status: STARTED
[20:59:24.662] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:26:0) after 7m35s
[21:06:59.681] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:26:0)
[21:06:59.705] Build status: STARTED
[21:06:59.705] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:27:0) after 9m16s
[21:16:15.725] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:27:0)
[21:16:15.757] Build status: STARTED
[21:16:15.757] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:28:0) after 1m4s
[21:17:19.772] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:28:0)
[21:17:19.798] Build status: STARTED
[21:17:19.798] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:29:0) after 7m29s
[21:24:48.817] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:29:0)
[21:24:48.861] Build status: STARTED
[21:24:48.861] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:30:0) after 1m11s
[21:25:59.882] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:30:0)
[21:25:59.905] Build status: STARTED
[21:25:59.905] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8842793982269688560:31:0) after 7m1s
[21:32:37.402] Received PubSub notification, asking Buildbucket for the build status
[21:32:37.427] Build:
{
"id": "8677363920361650705",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 24386,
"createdBy": "project:chromium",
"createTime": "2026-07-02T18:45:17.248818138Z",
"startTime": "2026-07-02T19:12:25.756149893Z",
"endTime": "2026-07-02T21:32:36.948798423Z",
"updateTime": "2026-07-02T21:32:36.948798423Z",
"status": "FAILURE",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "f4e4d1f36ed4c89f41f345580570034f1219860b",
"ref": "refs/heads/main"
}
},
"canary": true
}
[21:32:37.427] Invocation finished in 2h47m21.382574292s with status FAILED