[01:57:54.049] New invocation is queued and will start shortly
[01:57:55.130] Starting the invocation (attempt 1)
[01:57:55.156] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/bf39271c541763ae847ca4de0bfbec0b7e284044"
[01:57:55.156] Popped gitiles commit info from properties and tags
[01:57:55.156] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[01:57:55.156] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[01:57:55.156] Buildbucket request:
{
"requestId": "8832076321301494480",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "bf39271c541763ae847ca4de0bfbec0b7e284044",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8832076321301494480"
},
{
"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"
}
}
[01:57:57.554] Scheduled build:
{
"id": "8666646257992821889",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 45988,
"createdBy": "project:chromium",
"createTime": "2026-10-29T01:57:56.581063437Z",
"updateTime": "2026-10-29T01:57:57.277935732Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "bf39271c541763ae847ca4de0bfbec0b7e284044",
"ref": "refs/heads/main"
}
},
"canary": true
}
[01:57:57.554] Task URL: https://cr-buildbucket-dev.appspot.com/build/8666646257992821889
[01:57:57.554] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:2:0) after 7m34s
[01:57:58.166] Received PubSub notification, asking Buildbucket for the build status
[01:57:58.184] Build status: SCHEDULED
[02:05:31.574] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:2:0)
[02:05:31.607] Build status: SCHEDULED
[02:05:31.607] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:4:0) after 6m21s
[02:11:52.627] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:4:0)
[02:11:52.647] Build status: SCHEDULED
[02:11:52.647] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:5:0) after 2m55s
[02:14:47.686] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:5:0)
[02:14:47.717] Build status: SCHEDULED
[02:14:47.717] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:6:0) after 1m27s
[02:16:14.759] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:6:0)
[02:16:14.798] Build status: SCHEDULED
[02:16:14.799] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:7:0) after 6m0s
[02:22:14.844] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:7:0)
[02:22:14.868] Build status: SCHEDULED
[02:22:14.868] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:8:0) after 6m24s
[02:28:38.888] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:8:0)
[02:28:38.910] Build status: SCHEDULED
[02:28:38.910] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:9:0) after 2m27s
[02:31:05.943] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:9:0)
[02:31:05.967] Build status: SCHEDULED
[02:31:05.968] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:10:0) after 6m24s
[02:37:30.002] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:10:0)
[02:37:30.028] Build status: SCHEDULED
[02:37:30.028] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:11:0) after 7m31s
[02:37:32.296] Received PubSub notification, asking Buildbucket for the build status
[02:37:32.317] Build status: STARTED
[02:45:01.067] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:11:0)
[02:45:01.105] Build status: STARTED
[02:45:01.105] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:13:0) after 2m33s
[02:47:34.126] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:13:0)
[02:47:34.161] Build status: STARTED
[02:47:34.161] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:14:0) after 9m58s
[02:57:32.196] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:14:0)
[02:57:32.215] Build status: STARTED
[02:57:32.215] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:15:0) after 5m43s
[03:03:15.256] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:15:0)
[03:03:15.278] Build status: STARTED
[03:03:15.278] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:16:0) after 1m40s
[03:04:55.298] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:16:0)
[03:04:55.339] Build status: STARTED
[03:04:55.339] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:17:0) after 8m35s
[03:13:30.362] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:17:0)
[03:13:30.380] Build status: STARTED
[03:13:30.380] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:18:0) after 1m16s
[03:14:46.411] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:18:0)
[03:14:46.458] Build status: STARTED
[03:14:46.458] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:19:0) after 1m42s
[03:16:28.479] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:19:0)
[03:16:28.499] Build status: STARTED
[03:16:28.499] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:20:0) after 8m15s
[03:24:43.475] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:20:0)
[03:24:43.498] Build status: STARTED
[03:24:43.498] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:21:0) after 6m24s
[03:31:07.521] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:21:0)
[03:31:07.556] Build status: STARTED
[03:31:07.556] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8832076321301494480:22:0) after 5m28s
[03:32:28.926] Received PubSub notification, asking Buildbucket for the build status
[03:32:29.001] Build:
{
"id": "8666646257992821889",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 45988,
"createdBy": "project:chromium",
"createTime": "2026-10-29T01:57:56.581063437Z",
"startTime": "2026-10-29T02:37:31.965516995Z",
"endTime": "2026-10-29T03:32:28.412997175Z",
"updateTime": "2026-10-29T03:32:28.412997175Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "bf39271c541763ae847ca4de0bfbec0b7e284044",
"ref": "refs/heads/main"
}
},
"canary": true
}
[03:32:29.001] Invocation finished in 1h34m34.958852166s with status SUCCEEDED