[17:40:06.049] New invocation is queued and will start shortly
[17:40:07.118] Starting the invocation (attempt 1)
[17:40:07.158] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/9f27ccce5d52e409ce597d9322b4e329b781a578"
[17:40:07.158] Popped gitiles commit info from properties and tags
[17:40:07.158] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[17:40:07.178] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[17:40:07.178] Buildbucket request:
{
"requestId": "8865719114704527760",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "9f27ccce5d52e409ce597d9322b4e329b781a578",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8865719114704527760"
},
{
"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"
}
}
[17:40:08.072] Scheduled build:
{
"id": "8700289052776608193",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 20248,
"createdBy": "project:chromium",
"createTime": "2025-10-22T17:40:07.264587031Z",
"updateTime": "2025-10-22T17:40:07.264587031Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "9f27ccce5d52e409ce597d9322b4e329b781a578",
"ref": "refs/heads/main"
}
},
"canary": true
}
[17:40:08.072] Task URL: https://cr-buildbucket-dev.appspot.com/build/8700289052776608193
[17:40:08.072] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:2:0) after 7m28s
[17:40:09.043] Received PubSub notification, asking Buildbucket for the build status
[17:40:09.062] Build status: SCHEDULED
[17:47:36.093] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:2:0)
[17:47:36.112] Build status: SCHEDULED
[17:47:36.113] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:4:0) after 9m20s
[17:56:56.132] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:4:0)
[17:56:56.155] Build status: SCHEDULED
[17:56:56.155] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:5:0) after 3m1s
[17:59:57.176] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:5:0)
[17:59:57.200] Build status: SCHEDULED
[17:59:57.200] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:6:0) after 2m14s
[18:02:11.218] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:6:0)
[18:02:11.251] Build status: SCHEDULED
[18:02:11.251] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:7:0) after 1m22s
[18:03:33.288] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:7:0)
[18:03:33.308] Build status: SCHEDULED
[18:03:33.308] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:8:0) after 2m35s
[18:06:08.329] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:8:0)
[18:06:08.356] Build status: SCHEDULED
[18:06:08.357] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:9:0) after 3m10s
[18:09:18.372] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:9:0)
[18:09:18.393] Build status: SCHEDULED
[18:09:18.393] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:10:0) after 7m29s
[18:16:47.411] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:10:0)
[18:16:47.456] Build status: SCHEDULED
[18:16:47.456] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:11:0) after 3m36s
[18:17:19.629] Received PubSub notification, asking Buildbucket for the build status
[18:17:19.656] Build status: STARTED
[18:20:23.473] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:11:0)
[18:20:23.501] Build status: STARTED
[18:20:23.501] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:13:0) after 4m24s
[18:24:47.529] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:13:0)
[18:24:47.553] Build status: STARTED
[18:24:47.553] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:14:0) after 8m16s
[18:33:03.570] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:14:0)
[18:33:03.588] Build status: STARTED
[18:33:03.588] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:15:0) after 4m34s
[18:37:37.825] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:15:0)
[18:37:37.913] Build status: STARTED
[18:37:37.913] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:16:0) after 5m35s
[18:43:12.931] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:16:0)
[18:43:12.958] Build status: STARTED
[18:43:12.958] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:17:0) after 1m32s
[18:44:44.989] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:17:0)
[18:44:45.021] Build status: STARTED
[18:44:45.021] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:18:0) after 7m41s
[18:52:26.039] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:18:0)
[18:52:26.108] Build status: STARTED
[18:52:26.108] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:19:0) after 9m30s
[19:01:56.126] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:19:0)
[19:01:56.153] Build status: STARTED
[19:01:56.153] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:20:0) after 2m32s
[19:04:28.169] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:20:0)
[19:04:28.188] Build status: STARTED
[19:04:28.188] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:21:0) after 3m32s
[19:08:00.211] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:21:0)
[19:08:00.232] Build status: STARTED
[19:08:00.232] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:22:0) after 2m11s
[19:10:11.249] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:22:0)
[19:10:11.265] Build status: STARTED
[19:10:11.265] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:23:0) after 1m41s
[19:11:52.286] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:23:0)
[19:11:52.308] Build status: STARTED
[19:11:52.308] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:24:0) after 3m0s
[19:14:52.332] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:24:0)
[19:14:52.357] Build status: STARTED
[19:14:52.357] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:25:0) after 2m55s
[19:17:47.380] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:25:0)
[19:17:47.403] Build status: STARTED
[19:17:47.403] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:26:0) after 3m51s
[19:21:38.425] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:26:0)
[19:21:38.446] Build status: STARTED
[19:21:38.446] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:27:0) after 9m32s
[19:31:10.466] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:27:0)
[19:31:10.487] Build status: STARTED
[19:31:10.487] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:28:0) after 2m45s
[19:33:55.508] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:28:0)
[19:33:55.532] Build status: STARTED
[19:33:55.532] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:29:0) after 7m21s
[19:41:16.559] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:29:0)
[19:41:16.580] Build status: STARTED
[19:41:16.580] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:30:0) after 4m58s
[19:46:14.596] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:30:0)
[19:46:14.616] Build status: STARTED
[19:46:14.616] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865719114704527760:31:0) after 8m56s
[19:49:21.883] Received PubSub notification, asking Buildbucket for the build status
[19:49:21.911] Build:
{
"id": "8700289052776608193",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 20248,
"createdBy": "project:chromium",
"createTime": "2025-10-22T17:40:07.264587031Z",
"startTime": "2025-10-22T18:17:19.405713589Z",
"endTime": "2025-10-22T19:49:21.508534947Z",
"updateTime": "2025-10-22T19:49:21.508534947Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "9f27ccce5d52e409ce597d9322b4e329b781a578",
"ref": "refs/heads/main"
}
},
"canary": true
}
[19:49:21.912] Invocation finished in 2h9m15.86983958s with status SUCCEEDED