[22:35:28.050] New invocation is queued and will start shortly
[22:35:29.117] Starting the invocation (attempt 1)
[22:35:29.141] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/2e8d5759bc6d582060fc072c18f1bed6792fe882"
[22:35:29.141] Popped gitiles commit info from properties and tags
[22:35:29.141] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[22:35:29.141] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[22:35:29.141] Buildbucket request:
{
"requestId": "8850389644517048544",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "2e8d5759bc6d582060fc072c18f1bed6792fe882",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8850389644517048544"
},
{
"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"
}
}
[22:35:29.829] Scheduled build:
{
"id": "8684959582652844545",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 22590,
"createdBy": "project:chromium",
"createTime": "2026-04-09T22:35:29.205663812Z",
"updateTime": "2026-04-09T22:35:29.205663812Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "2e8d5759bc6d582060fc072c18f1bed6792fe882",
"ref": "refs/heads/main"
}
},
"canary": true
}
[22:35:29.829] Task URL: https://cr-buildbucket-dev.appspot.com/build/8684959582652844545
[22:35:29.829] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:2:0) after 7m14s
[22:35:30.584] Received PubSub notification, asking Buildbucket for the build status
[22:35:30.609] Build status: SCHEDULED
[22:42:43.845] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:2:0)
[22:42:43.874] Build status: SCHEDULED
[22:42:43.874] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:4:0) after 7m8s
[22:49:51.917] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:4:0)
[22:49:51.934] Build status: SCHEDULED
[22:49:51.934] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:5:0) after 7m12s
[22:57:03.952] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:5:0)
[22:57:03.979] Build status: SCHEDULED
[22:57:03.979] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:6:0) after 5m9s
[23:02:12.996] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:6:0)
[23:02:13.015] Build status: SCHEDULED
[23:02:13.015] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:7:0) after 1m56s
[23:04:09.034] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:7:0)
[23:04:09.068] Build status: SCHEDULED
[23:04:09.068] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:8:0) after 5m57s
[23:10:06.084] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:8:0)
[23:10:06.106] Build status: SCHEDULED
[23:10:06.106] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:9:0) after 7m27s
[23:17:33.126] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:9:0)
[23:17:33.150] Build status: SCHEDULED
[23:17:33.150] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:10:0) after 5m6s
[23:20:08.388] Received PubSub notification, asking Buildbucket for the build status
[23:20:08.414] Build status: STARTED
[23:22:39.167] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:10:0)
[23:22:39.184] Build status: STARTED
[23:22:39.185] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:12:0) after 9m44s
[23:32:23.200] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:12:0)
[23:32:23.225] Build status: STARTED
[23:32:23.225] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:13:0) after 3m8s
[23:35:31.244] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:13:0)
[23:35:31.269] Build status: STARTED
[23:35:31.269] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:14:0) after 7m15s
[23:42:46.286] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:14:0)
[23:42:46.308] Build status: STARTED
[23:42:46.308] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:15:0) after 5m3s
[23:47:49.328] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:15:0)
[23:47:49.354] Build status: STARTED
[23:47:49.354] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:16:0) after 6m34s
[23:54:23.371] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:16:0)
[23:54:23.387] Build status: STARTED
[23:54:23.387] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:17:0) after 2m5s
[23:56:28.404] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:17:0)
[23:56:28.433] Build status: STARTED
[23:56:28.433] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:18:0) after 2m46s
[23:59:14.451] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:18:0)
[23:59:14.472] Build status: STARTED
[23:59:14.472] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:19:0) after 4m47s
[00:04:01.490] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:19:0)
[00:04:01.508] Build status: STARTED
[00:04:01.508] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:20:0) after 7m26s
[00:11:28.480] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:20:0)
[00:11:28.506] Build status: STARTED
[00:11:28.506] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:21:0) after 7m46s
[00:19:14.540] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:21:0)
[00:19:14.560] Build status: STARTED
[00:19:14.560] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:22:0) after 3m46s
[00:23:00.578] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:22:0)
[00:23:00.614] Build status: STARTED
[00:23:00.614] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:23:0) after 1m33s
[00:24:33.633] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:23:0)
[00:24:33.654] Build status: STARTED
[00:24:33.654] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:24:0) after 5m1s
[00:29:34.672] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:24:0)
[00:29:34.694] Build status: STARTED
[00:29:34.694] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:25:0) after 5m49s
[00:35:23.722] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:25:0)
[00:35:23.747] Build status: STARTED
[00:35:23.747] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:26:0) after 7m34s
[00:42:57.973] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:26:0)
[00:42:58.009] Build status: STARTED
[00:42:58.009] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:27:0) after 2m54s
[00:45:52.030] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:27:0)
[00:45:52.081] Build status: STARTED
[00:45:52.081] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850389644517048544:28:0) after 5m15s
[00:50:59.302] Received PubSub notification, asking Buildbucket for the build status
[00:50:59.389] Build:
{
"id": "8684959582652844545",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 22590,
"createdBy": "project:chromium",
"createTime": "2026-04-09T22:35:29.205663812Z",
"startTime": "2026-04-09T23:20:07.379745002Z",
"endTime": "2026-04-10T00:50:58.034510309Z",
"updateTime": "2026-04-10T00:50:58.034510309Z",
"status": "FAILURE",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "2e8d5759bc6d582060fc072c18f1bed6792fe882",
"ref": "refs/heads/main"
}
},
"canary": true
}
[00:50:59.389] Invocation finished in 2h15m31.344704077s with status FAILED