[15:40:18.073] New invocation is queued and will start shortly
[15:40:19.141] Starting the invocation (attempt 1)
[15:40:19.170] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/4b4aca55cb60050b7518d84ad68bcabd2c392733"
[15:40:19.170] Popped gitiles commit info from properties and tags
[15:40:19.170] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[15:40:19.171] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[15:40:19.171] Buildbucket request:
{
"requestId": "8868353963868642608",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "4b4aca55cb60050b7518d84ad68bcabd2c392733",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8868353963868642608"
},
{
"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"
}
}
[15:40:20.197] Scheduled build:
{
"id": "8702923902005144593",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 28494,
"createdBy": "project:chromium",
"createTime": "2025-09-23T15:40:19.227654785Z",
"updateTime": "2025-09-23T15:40:19.227654785Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "4b4aca55cb60050b7518d84ad68bcabd2c392733",
"ref": "refs/heads/main"
}
},
"canary": true
}
[15:40:20.197] Task URL: https://cr-buildbucket-dev.appspot.com/build/8702923902005144593
[15:40:20.197] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:2:0) after 5m50s
[15:40:21.131] Received PubSub notification, asking Buildbucket for the build status
[15:40:21.151] Build status: SCHEDULED
[15:46:10.225] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:2:0)
[15:46:10.254] Build status: SCHEDULED
[15:46:10.254] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:4:0) after 7m55s
[15:54:05.273] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:4:0)
[15:54:05.299] Build status: SCHEDULED
[15:54:05.299] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:5:0) after 3m32s
[15:57:37.318] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:5:0)
[15:57:37.340] Build status: SCHEDULED
[15:57:37.340] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:6:0) after 6m3s
[16:03:40.364] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:6:0)
[16:03:40.393] Build status: SCHEDULED
[16:03:40.393] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:7:0) after 2m39s
[16:06:19.420] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:7:0)
[16:06:19.444] Build status: SCHEDULED
[16:06:19.444] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:8:0) after 5m12s
[16:11:31.465] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:8:0)
[16:11:31.485] Build status: SCHEDULED
[16:11:31.485] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:9:0) after 9m6s
[16:17:30.875] Received PubSub notification, asking Buildbucket for the build status
[16:17:30.900] Build status: STARTED
[16:20:37.501] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:9:0)
[16:20:37.551] Build status: STARTED
[16:20:37.551] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:11:0) after 6m55s
[16:27:32.572] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:11:0)
[16:27:32.604] Build status: STARTED
[16:27:32.604] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:12:0) after 4m6s
[16:31:38.623] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:12:0)
[16:31:38.648] Build status: STARTED
[16:31:38.648] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:13:0) after 8m45s
[16:40:23.670] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:13:0)
[16:40:23.798] Build status: STARTED
[16:40:23.798] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:14:0) after 2m8s
[16:42:31.820] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:14:0)
[16:42:31.850] Build status: STARTED
[16:42:31.850] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:15:0) after 3m49s
[16:46:20.877] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:15:0)
[16:46:20.910] Build status: STARTED
[16:46:20.910] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:16:0) after 5m46s
[16:52:06.927] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:16:0)
[16:52:06.988] Build status: STARTED
[16:52:06.988] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:17:0) after 1m45s
[16:53:52.005] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:17:0)
[16:53:52.031] Build status: STARTED
[16:53:52.031] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:18:0) after 9m41s
[17:03:33.049] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:18:0)
[17:03:33.067] Build status: STARTED
[17:03:33.067] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:19:0) after 5m27s
[17:09:00.098] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:19:0)
[17:09:00.123] Build status: STARTED
[17:09:00.123] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:20:0) after 7m19s
[17:16:19.143] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:20:0)
[17:16:19.168] Build status: STARTED
[17:16:19.168] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:21:0) after 6m13s
[17:22:32.185] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:21:0)
[17:22:32.212] Build status: STARTED
[17:22:32.212] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8868353963868642608:22:0) after 9m4s
[17:31:30.040] Received PubSub notification, asking Buildbucket for the build status
[17:31:30.149] Build:
{
"id": "8702923902005144593",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 28494,
"createdBy": "project:chromium",
"createTime": "2025-09-23T15:40:19.227654785Z",
"startTime": "2025-09-23T16:17:30.662463958Z",
"endTime": "2025-09-23T17:31:29.723630899Z",
"updateTime": "2025-09-23T17:31:29.723630899Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "4b4aca55cb60050b7518d84ad68bcabd2c392733",
"ref": "refs/heads/main"
}
},
"canary": true
}
[17:31:30.149] Invocation finished in 1h51m12.083476628s with status SUCCEEDED