[22:17:04.055] New invocation is queued and will start shortly
[22:17:05.139] Starting the invocation (attempt 1)
[22:17:05.171] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/5753bf47cb3ef7010e93f7c9b394da0aba55f521"
[22:17:05.171] Popped gitiles commit info from properties and tags
[22:17:05.171] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[22:17:05.171] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[22:17:05.171] Buildbucket request:
{
"requestId": "8904567788046787456",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5753bf47cb3ef7010e93f7c9b394da0aba55f521",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8904567788046787456"
},
{
"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"
}
}
[22:17:06.354] Scheduled build:
{
"id": "8739137726116954641",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 9051,
"createdBy": "project:chromium",
"createTime": "2024-08-19T22:17:05.273066491Z",
"updateTime": "2024-08-19T22:17:05.273066491Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5753bf47cb3ef7010e93f7c9b394da0aba55f521",
"ref": "refs/heads/main"
}
},
"canary": true
}
[22:17:06.354] Task URL: https://cr-buildbucket-dev.appspot.com/build/8739137726116954641
[22:17:06.354] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:2:0) after 8m7s
[22:17:07.292] Received PubSub notification, asking Buildbucket for the build status
[22:17:07.325] Build status: SCHEDULED
[22:25:13.466] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:2:0)
[22:25:13.498] Build status: SCHEDULED
[22:25:13.498] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:4:0) after 9m44s
[22:34:57.520] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:4:0)
[22:34:57.561] Build status: SCHEDULED
[22:34:57.561] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:5:0) after 6m58s
[22:41:55.581] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:5:0)
[22:41:55.608] Build status: SCHEDULED
[22:41:55.608] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:6:0) after 6m58s
[22:48:53.628] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:6:0)
[22:48:53.671] Build status: SCHEDULED
[22:48:53.671] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:7:0) after 9m57s
[22:58:50.690] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:7:0)
[22:58:50.746] Build status: SCHEDULED
[22:58:50.746] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:8:0) after 9m9s
[23:06:31.660] Received PubSub notification, asking Buildbucket for the build status
[23:06:31.700] Build status: STARTED
[23:07:59.770] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:8:0)
[23:07:59.838] Build status: STARTED
[23:07:59.838] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:10:0) after 2m8s
[23:10:07.861] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:10:0)
[23:10:07.892] Build status: STARTED
[23:10:07.892] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:11:0) after 5m30s
[23:15:37.909] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:11:0)
[23:15:37.941] Build status: STARTED
[23:15:37.941] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:12:0) after 9m52s
[23:25:29.959] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:12:0)
[23:25:30.010] Build status: STARTED
[23:25:30.010] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:13:0) after 5m25s
[23:30:55.029] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:13:0)
[23:30:55.086] Build status: STARTED
[23:30:55.086] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:14:0) after 5m32s
[23:36:27.113] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:14:0)
[23:36:27.188] Build status: STARTED
[23:36:27.188] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:15:0) after 6m8s
[23:42:35.216] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:15:0)
[23:42:35.250] Build status: STARTED
[23:42:35.250] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:16:0) after 8m29s
[23:51:04.280] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:16:0)
[23:51:04.324] Build status: STARTED
[23:51:04.324] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:17:0) after 2m33s
[23:53:37.346] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:17:0)
[23:53:37.373] Build status: STARTED
[23:53:37.373] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:18:0) after 1m21s
[23:54:58.392] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:18:0)
[23:54:58.428] Build status: STARTED
[23:54:58.428] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:19:0) after 7m3s
[00:02:01.452] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:19:0)
[00:02:01.498] Build status: STARTED
[00:02:01.498] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:20:0) after 9m38s
[00:11:39.519] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:20:0)
[00:11:39.555] Build status: STARTED
[00:11:39.556] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:21:0) after 6m23s
[00:18:02.574] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:21:0)
[00:18:02.602] Build status: STARTED
[00:18:02.602] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:22:0) after 1m22s
[00:19:24.622] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:22:0)
[00:19:24.660] Build status: STARTED
[00:19:24.660] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:23:0) after 6m17s
[00:25:41.681] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:23:0)
[00:25:41.701] Build status: STARTED
[00:25:41.701] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:24:0) after 8m14s
[00:33:55.723] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:24:0)
[00:33:55.799] Build status: STARTED
[00:33:55.799] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:25:0) after 1m30s
[00:35:25.855] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:25:0)
[00:35:25.885] Build status: STARTED
[00:35:25.885] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:26:0) after 7m5s
[00:42:30.908] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:26:0)
[00:42:31.001] Build status: STARTED
[00:42:31.001] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:27:0) after 4m31s
[00:47:02.028] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:27:0)
[00:47:02.099] Build status: STARTED
[00:47:02.099] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:28:0) after 8m28s
[00:55:30.122] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:28:0)
[00:55:30.171] Build status: STARTED
[00:55:30.173] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:29:0) after 5m10s
[01:00:40.201] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:29:0)
[01:00:40.270] Build status: STARTED
[01:00:40.270] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:30:0) after 1m36s
[01:02:16.287] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:30:0)
[01:02:16.321] Build status: STARTED
[01:02:16.321] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8904567788046787456:31:0) after 4m17s
[01:04:04.076] Received PubSub notification, asking Buildbucket for the build status
[01:04:04.105] Build:
{
"id": "8739137726116954641",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 9051,
"createdBy": "project:chromium",
"createTime": "2024-08-19T22:17:05.273066491Z",
"startTime": "2024-08-19T23:06:31.316383668Z",
"endTime": "2024-08-20T01:04:03.683730780Z",
"updateTime": "2024-08-20T01:04:03.683730780Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5753bf47cb3ef7010e93f7c9b394da0aba55f521",
"ref": "refs/heads/main"
}
},
"canary": true
}
[01:04:04.105] Invocation finished in 2h47m0.055758708s with status SUCCEEDED