[09:26:47.048] New invocation is queued and will start shortly
[09:26:48.115] Starting the invocation (attempt 1)
[09:26:48.138] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/b6d815c406f82c8b5bd9a406ae5634ec0cf4894b"
[09:26:48.138] Popped gitiles commit info from properties and tags
[09:26:48.138] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[09:26:48.139] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[09:26:48.139] Buildbucket request:
{
"requestId": "8831323304271411264",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "b6d815c406f82c8b5bd9a406ae5634ec0cf4894b",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8831323304271411264"
},
{
"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"
}
}
[09:26:50.264] Scheduled build:
{
"id": "8665893241312451889",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 46405,
"createdBy": "project:chromium",
"createTime": "2026-11-06T09:26:49.249689170Z",
"updateTime": "2026-11-06T09:26:50.032105421Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "b6d815c406f82c8b5bd9a406ae5634ec0cf4894b",
"ref": "refs/heads/main"
}
},
"canary": true
}
[09:26:50.264] Task URL: https://cr-buildbucket-dev.appspot.com/build/8665893241312451889
[09:26:50.264] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:2:0) after 3m16s
[09:26:51.001] Received PubSub notification, asking Buildbucket for the build status
[09:26:51.034] Build status: SCHEDULED
[09:30:06.279] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:2:0)
[09:30:06.309] Build status: SCHEDULED
[09:30:06.309] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:4:0) after 1m14s
[09:31:20.323] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:4:0)
[09:31:20.368] Build status: SCHEDULED
[09:31:20.368] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:5:0) after 5m44s
[09:37:04.395] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:5:0)
[09:37:04.436] Build status: SCHEDULED
[09:37:04.436] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:6:0) after 8m47s
[09:45:51.449] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:6:0)
[09:45:51.470] Build status: SCHEDULED
[09:45:51.470] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:7:0) after 7m2s
[09:52:53.490] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:7:0)
[09:52:53.510] Build status: SCHEDULED
[09:52:53.510] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:8:0) after 1m24s
[09:54:17.526] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:8:0)
[09:54:17.546] Build status: SCHEDULED
[09:54:17.547] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:9:0) after 5m0s
[09:59:17.567] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:9:0)
[09:59:17.598] Build status: SCHEDULED
[09:59:17.598] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:10:0) after 2m11s
[10:01:28.615] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:10:0)
[10:01:28.639] Build status: SCHEDULED
[10:01:28.639] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:11:0) after 9m11s
[10:10:39.652] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:11:0)
[10:10:39.677] Build status: SCHEDULED
[10:10:39.677] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:12:0) after 9m7s
[10:13:26.093] Received PubSub notification, asking Buildbucket for the build status
[10:13:26.120] Build status: STARTED
[10:19:46.693] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:12:0)
[10:19:46.737] Build status: STARTED
[10:19:46.737] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:14:0) after 9m32s
[10:29:18.752] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:14:0)
[10:29:18.786] Build status: STARTED
[10:29:18.786] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:15:0) after 8m2s
[10:37:20.802] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:15:0)
[10:37:20.824] Build status: STARTED
[10:37:20.824] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:16:0) after 5m22s
[10:42:42.843] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:16:0)
[10:42:42.874] Build status: STARTED
[10:42:42.874] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:17:0) after 5m31s
[10:48:13.889] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:17:0)
[10:48:13.911] Build status: STARTED
[10:48:13.911] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:18:0) after 2m0s
[10:50:13.928] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:18:0)
[10:50:13.946] Build status: STARTED
[10:50:13.946] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:19:0) after 7m43s
[10:57:56.964] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:19:0)
[10:57:56.996] Build status: STARTED
[10:57:56.997] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:20:0) after 5m49s
[11:03:46.013] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:20:0)
[11:03:46.034] Build status: STARTED
[11:03:46.034] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:21:0) after 4m8s
[11:07:54.051] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:21:0)
[11:07:54.080] Build status: STARTED
[11:07:54.080] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8831323304271411264:22:0) after 8m48s
[11:09:05.621] Received PubSub notification, asking Buildbucket for the build status
[11:09:05.646] Build:
{
"id": "8665893241312451889",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 46405,
"createdBy": "project:chromium",
"createTime": "2026-11-06T09:26:49.249689170Z",
"startTime": "2026-11-06T10:13:25.407347835Z",
"endTime": "2026-11-06T11:09:04.974254181Z",
"updateTime": "2026-11-06T11:09:04.974254181Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "b6d815c406f82c8b5bd9a406ae5634ec0cf4894b",
"ref": "refs/heads/main"
}
},
"canary": true
}
[11:09:05.646] Invocation finished in 1h42m18.601786121s with status SUCCEEDED