[04:31:36.042] New invocation is queued and will start shortly
[04:31:37.097] Starting the invocation (attempt 1)
[04:31:37.122] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/f9a9a1ebd95290bc105ee7485f28816b8f3c484d"
[04:31:37.123] Popped gitiles commit info from properties and tags
[04:31:37.123] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[04:31:37.123] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[04:31:37.123] Buildbucket request:
{
"requestId": "8851182611248797632",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "f9a9a1ebd95290bc105ee7485f28816b8f3c484d",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8851182611248797632"
},
{
"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"
}
}
[04:31:38.039] Scheduled build:
{
"id": "8685752549386677521",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 36085,
"createdBy": "project:chromium",
"createTime": "2026-04-01T04:31:37.197036300Z",
"updateTime": "2026-04-01T04:31:37.197036300Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "f9a9a1ebd95290bc105ee7485f28816b8f3c484d",
"ref": "refs/heads/main"
}
},
"canary": true
}
[04:31:38.039] Task URL: https://cr-buildbucket-dev.appspot.com/build/8685752549386677521
[04:31:38.039] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:2:0) after 1m48s
[04:31:38.863] Received PubSub notification, asking Buildbucket for the build status
[04:31:38.888] Build status: SCHEDULED
[04:33:26.053] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:2:0)
[04:33:26.082] Build status: SCHEDULED
[04:33:26.082] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:4:0) after 6m55s
[04:40:21.097] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:4:0)
[04:40:21.121] Build status: SCHEDULED
[04:40:21.121] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:5:0) after 2m10s
[04:42:31.138] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:5:0)
[04:42:31.171] Build status: SCHEDULED
[04:42:31.171] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:6:0) after 7m30s
[04:50:01.665] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:6:0)
[04:50:01.684] Build status: SCHEDULED
[04:50:01.684] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:7:0) after 6m40s
[04:56:41.870] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:7:0)
[04:56:41.891] Build status: SCHEDULED
[04:56:41.891] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:8:0) after 4m54s
[05:01:35.910] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:8:0)
[05:01:35.931] Build status: SCHEDULED
[05:01:35.931] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:9:0) after 4m30s
[05:06:05.952] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:9:0)
[05:06:05.972] Build status: SCHEDULED
[05:06:05.972] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:10:0) after 3m27s
[05:09:32.988] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:10:0)
[05:09:33.009] Build status: SCHEDULED
[05:09:33.010] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:11:0) after 9m27s
[05:12:06.260] Received PubSub notification, asking Buildbucket for the build status
[05:12:06.292] Build status: STARTED
[05:19:00.024] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:11:0)
[05:19:00.057] Build status: STARTED
[05:19:00.057] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:13:0) after 1m57s
[05:20:57.070] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:13:0)
[05:20:57.098] Build status: STARTED
[05:20:57.098] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:14:0) after 3m4s
[05:24:01.111] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:14:0)
[05:24:01.145] Build status: STARTED
[05:24:01.146] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:15:0) after 3m2s
[05:27:03.160] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:15:0)
[05:27:03.188] Build status: STARTED
[05:27:03.188] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:16:0) after 7m4s
[05:34:07.206] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:16:0)
[05:34:07.227] Build status: STARTED
[05:34:07.227] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:17:0) after 8m39s
[05:42:46.242] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:17:0)
[05:42:46.262] Build status: STARTED
[05:42:46.262] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:18:0) after 8m9s
[05:50:55.278] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:18:0)
[05:50:55.305] Build status: STARTED
[05:50:55.305] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:19:0) after 9m50s
[06:00:45.320] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:19:0)
[06:00:45.381] Build status: STARTED
[06:00:45.381] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:20:0) after 4m36s
[06:05:21.396] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:20:0)
[06:05:21.417] Build status: STARTED
[06:05:21.417] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:21:0) after 3m39s
[06:09:00.433] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:21:0)
[06:09:00.473] Build status: STARTED
[06:09:00.473] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:22:0) after 2m52s
[06:11:52.518] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:22:0)
[06:11:52.547] Build status: STARTED
[06:11:52.547] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:23:0) after 5m47s
[06:17:39.580] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:23:0)
[06:17:39.650] Build status: STARTED
[06:17:39.650] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:24:0) after 6m46s
[06:24:25.667] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:24:0)
[06:24:25.689] Build status: STARTED
[06:24:25.689] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:25:0) after 5m19s
[06:29:44.708] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:25:0)
[06:29:44.736] Build status: STARTED
[06:29:44.736] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:26:0) after 2m46s
[06:32:30.751] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:26:0)
[06:32:30.774] Build status: STARTED
[06:32:30.774] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:27:0) after 1m44s
[06:34:14.805] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:27:0)
[06:34:14.835] Build status: STARTED
[06:34:14.835] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:28:0) after 3m4s
[06:37:18.849] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:28:0)
[06:37:18.973] Build status: STARTED
[06:37:18.973] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8851182611248797632:29:0) after 4m48s
[06:37:32.284] Received PubSub notification, asking Buildbucket for the build status
[06:37:32.307] Build:
{
"id": "8685752549386677521",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 36085,
"createdBy": "project:chromium",
"createTime": "2026-04-01T04:31:37.197036300Z",
"startTime": "2026-04-01T05:12:06.020704107Z",
"endTime": "2026-04-01T06:37:23.947414309Z",
"updateTime": "2026-04-01T06:37:23.947414309Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "f9a9a1ebd95290bc105ee7485f28816b8f3c484d",
"ref": "refs/heads/main"
}
},
"canary": true
}
[06:37:32.307] Invocation finished in 2h5m56.269594127s with status SUCCEEDED