[11:36:12.051] New invocation is queued and will start shortly
[11:36:13.119] Starting the invocation (attempt 1)
[11:36:13.147] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/77a0b8b49613ad643cd2aaa6d0a2a9fbbd3c7a8b"
[11:36:13.147] Popped gitiles commit info from properties and tags
[11:36:13.147] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[11:36:13.147] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[11:36:13.147] Buildbucket request:
{
"requestId": "8850612315919741792",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "77a0b8b49613ad643cd2aaa6d0a2a9fbbd3c7a8b",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8850612315919741792"
},
{
"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"
}
}
[11:36:14.186] Scheduled build:
{
"id": "8685182254059462641",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 22565,
"createdBy": "project:chromium",
"createTime": "2026-04-07T11:36:13.204678826Z",
"updateTime": "2026-04-07T11:36:13.204678826Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "77a0b8b49613ad643cd2aaa6d0a2a9fbbd3c7a8b",
"ref": "refs/heads/main"
}
},
"canary": true
}
[11:36:14.186] Task URL: https://cr-buildbucket-dev.appspot.com/build/8685182254059462641
[11:36:14.186] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:2:0) after 8m2s
[11:36:15.207] Received PubSub notification, asking Buildbucket for the build status
[11:36:15.231] Build status: SCHEDULED
[11:44:16.206] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:2:0)
[11:44:16.237] Build status: SCHEDULED
[11:44:16.237] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:4:0) after 4m43s
[11:47:17.312] Received PubSub notification, asking Buildbucket for the build status
[11:47:17.344] Build status: STARTED
[11:48:59.265] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:4:0)
[11:48:59.287] Build status: STARTED
[11:48:59.287] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:6:0) after 2m40s
[11:51:39.307] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:6:0)
[11:51:39.327] Build status: STARTED
[11:51:39.327] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:7:0) after 1m25s
[11:53:04.345] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:7:0)
[11:53:04.367] Build status: STARTED
[11:53:04.368] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:8:0) after 6m25s
[11:59:29.384] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:8:0)
[11:59:29.401] Build status: STARTED
[11:59:29.401] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:9:0) after 1m22s
[12:00:51.423] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:9:0)
[12:00:51.449] Build status: STARTED
[12:00:51.449] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:10:0) after 2m53s
[12:03:44.465] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:10:0)
[12:03:44.490] Build status: STARTED
[12:03:44.490] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:11:0) after 1m12s
[12:04:56.506] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:11:0)
[12:04:56.527] Build status: STARTED
[12:04:56.527] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:12:0) after 1m50s
[12:06:46.550] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:12:0)
[12:06:46.575] Build status: STARTED
[12:06:46.575] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:13:0) after 2m0s
[12:08:46.593] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:13:0)
[12:08:46.626] Build status: STARTED
[12:08:46.626] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:14:0) after 8m48s
[12:17:34.640] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:14:0)
[12:17:34.669] Build status: STARTED
[12:17:34.669] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:15:0) after 7m37s
[12:25:11.686] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:15:0)
[12:25:11.710] Build status: STARTED
[12:25:11.710] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:16:0) after 1m23s
[12:26:34.730] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:16:0)
[12:26:34.753] Build status: STARTED
[12:26:34.753] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:17:0) after 2m28s
[12:29:02.779] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:17:0)
[12:29:02.800] Build status: STARTED
[12:29:02.800] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:18:0) after 4m39s
[12:33:41.844] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:18:0)
[12:33:41.863] Build status: STARTED
[12:33:41.863] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:19:0) after 7m32s
[12:41:13.882] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:19:0)
[12:41:13.904] Build status: STARTED
[12:41:13.904] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:20:0) after 5m52s
[12:47:05.923] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:20:0)
[12:47:05.955] Build status: STARTED
[12:47:05.955] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:21:0) after 5m3s
[12:52:08.971] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:21:0)
[12:52:08.990] Build status: STARTED
[12:52:08.990] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:22:0) after 6m36s
[12:58:45.018] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:22:0)
[12:58:45.067] Build status: STARTED
[12:58:45.067] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:23:0) after 1m54s
[13:00:39.112] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:23:0)
[13:00:39.134] Build status: STARTED
[13:00:39.134] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:24:0) after 5m32s
[13:06:11.155] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:24:0)
[13:06:11.207] Build status: STARTED
[13:06:11.207] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:25:0) after 2m59s
[13:09:10.227] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:25:0)
[13:09:10.252] Build status: STARTED
[13:09:10.252] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:26:0) after 1m5s
[13:10:15.270] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:26:0)
[13:10:15.293] Build status: STARTED
[13:10:15.293] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:27:0) after 1m53s
[13:12:08.313] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:27:0)
[13:12:08.348] Build status: STARTED
[13:12:08.348] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:28:0) after 2m51s
[13:14:59.371] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:28:0)
[13:14:59.468] Build status: STARTED
[13:14:59.468] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:29:0) after 6m52s
[13:21:51.490] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:29:0)
[13:21:51.513] Build status: STARTED
[13:21:51.513] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:30:0) after 1m36s
[13:23:27.535] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:30:0)
[13:23:27.565] Build status: STARTED
[13:23:27.565] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8850612315919741792:31:0) after 2m39s
[13:25:22.554] Received PubSub notification, asking Buildbucket for the build status
[13:25:22.578] Build:
{
"id": "8685182254059462641",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 22565,
"createdBy": "project:chromium",
"createTime": "2026-04-07T11:36:13.204678826Z",
"startTime": "2026-04-07T11:47:15.499038985Z",
"endTime": "2026-04-07T13:25:11.866648916Z",
"updateTime": "2026-04-07T13:25:11.866648916Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "77a0b8b49613ad643cd2aaa6d0a2a9fbbd3c7a8b",
"ref": "refs/heads/main"
}
},
"canary": true
}
[13:25:22.578] Invocation finished in 1h49m10.531504277s with status SUCCEEDED