[16:45:21.061] New invocation is queued and will start shortly
[16:45:22.131] Starting the invocation (attempt 1)
[16:45:22.155] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/9b301aca5be44c7357d622d1667cea06384e1d02"
[16:45:22.155] Popped gitiles commit info from properties and tags
[16:45:22.155] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[16:45:22.155] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[16:45:22.155] Buildbucket request:
{
"requestId": "8866719125895205680",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "9b301aca5be44c7357d622d1667cea06384e1d02",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8866719125895205680"
},
{
"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"
}
}
[16:45:22.922] Scheduled build:
{
"id": "8701289064038081281",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 20109,
"createdBy": "project:chromium",
"createTime": "2025-10-11T16:45:22.208474327Z",
"updateTime": "2025-10-11T16:45:22.208474327Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "9b301aca5be44c7357d622d1667cea06384e1d02",
"ref": "refs/heads/main"
}
},
"canary": true
}
[16:45:22.922] Task URL: https://cr-buildbucket-dev.appspot.com/build/8701289064038081281
[16:45:22.922] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:2:0) after 1m32s
[16:45:22.995] Received PubSub notification, asking Buildbucket for the build status
[16:45:23.016] Build status: SCHEDULED
[16:46:54.938] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:2:0)
[16:46:54.957] Build status: SCHEDULED
[16:46:54.957] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:4:0) after 2m48s
[16:49:42.973] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:4:0)
[16:49:43.003] Build status: SCHEDULED
[16:49:43.003] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:5:0) after 6m9s
[16:55:52.020] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:5:0)
[16:55:52.042] Build status: SCHEDULED
[16:55:52.042] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:6:0) after 5m16s
[17:01:08.055] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:6:0)
[17:01:08.085] Build status: SCHEDULED
[17:01:08.085] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:7:0) after 2m10s
[17:03:18.101] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:7:0)
[17:03:18.134] Build status: SCHEDULED
[17:03:18.134] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:8:0) after 9m58s
[17:04:23.268] Received PubSub notification, asking Buildbucket for the build status
[17:04:23.291] Build status: STARTED
[17:13:16.150] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:8:0)
[17:13:16.169] Build status: STARTED
[17:13:16.169] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:10:0) after 5m23s
[17:18:39.183] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:10:0)
[17:18:39.204] Build status: STARTED
[17:18:39.204] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:11:0) after 3m9s
[17:21:48.226] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:11:0)
[17:21:48.247] Build status: STARTED
[17:21:48.247] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:12:0) after 8m58s
[17:30:46.262] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:12:0)
[17:30:46.322] Build status: STARTED
[17:30:46.322] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:13:0) after 5m59s
[17:36:45.356] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:13:0)
[17:36:45.391] Build status: STARTED
[17:36:45.391] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:14:0) after 1m27s
[17:38:12.405] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:14:0)
[17:38:12.436] Build status: STARTED
[17:38:12.436] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:15:0) after 8m27s
[17:46:39.449] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:15:0)
[17:46:39.464] Build status: STARTED
[17:46:39.464] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:16:0) after 4m9s
[17:50:48.483] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:16:0)
[17:50:48.542] Build status: STARTED
[17:50:48.542] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:17:0) after 8m0s
[17:58:48.558] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:17:0)
[17:58:48.583] Build status: STARTED
[17:58:48.584] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:18:0) after 3m32s
[18:02:20.599] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:18:0)
[18:02:20.628] Build status: STARTED
[18:02:20.628] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:19:0) after 2m42s
[18:05:02.644] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:19:0)
[18:05:02.661] Build status: STARTED
[18:05:02.661] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:20:0) after 7m10s
[18:12:12.677] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:20:0)
[18:12:12.704] Build status: STARTED
[18:12:12.704] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:21:0) after 6m59s
[18:19:11.724] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:21:0)
[18:19:11.751] Build status: STARTED
[18:19:11.751] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:22:0) after 4m32s
[18:23:43.766] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:22:0)
[18:23:43.790] Build status: STARTED
[18:23:43.790] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:23:0) after 1m3s
[18:24:46.804] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:23:0)
[18:24:46.831] Build status: STARTED
[18:24:46.831] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:24:0) after 9m47s
[18:34:33.847] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:24:0)
[18:34:33.869] Build status: STARTED
[18:34:33.869] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:25:0) after 8m47s
[18:43:20.886] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:25:0)
[18:43:20.907] Build status: STARTED
[18:43:20.907] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:26:0) after 1m12s
[18:44:32.927] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:26:0)
[18:44:32.949] Build status: STARTED
[18:44:32.949] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:27:0) after 8m18s
[18:52:50.965] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:27:0)
[18:52:50.985] Build status: STARTED
[18:52:50.985] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:28:0) after 9m38s
[19:02:29.001] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:28:0)
[19:02:29.208] Build status: STARTED
[19:02:29.208] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:29:0) after 5m5s
[19:07:34.223] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:29:0)
[19:07:34.242] Build status: STARTED
[19:07:34.242] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:30:0) after 7m54s
[19:15:28.258] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:30:0)
[19:15:28.285] Build status: STARTED
[19:15:28.285] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8866719125895205680:31:0) after 6m31s
[19:15:45.289] Received PubSub notification, asking Buildbucket for the build status
[19:15:45.314] Build:
{
"id": "8701289064038081281",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 20109,
"createdBy": "project:chromium",
"createTime": "2025-10-11T16:45:22.208474327Z",
"startTime": "2025-10-11T17:04:20.274878171Z",
"endTime": "2025-10-11T19:15:44.511783947Z",
"updateTime": "2025-10-11T19:15:44.511783947Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "9b301aca5be44c7357d622d1667cea06384e1d02",
"ref": "refs/heads/main"
}
},
"canary": true
}
[19:15:45.314] Invocation finished in 2h30m24.260597082s with status SUCCEEDED