[22:18:14.044] New invocation is queued and will start shortly
[22:18:15.102] Starting the invocation (attempt 1)
[22:18:15.126] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/c52d8c9dd10585a7cb325559cf6a0627b3bb80ca"
[22:18:15.126] Popped gitiles commit info from properties and tags
[22:18:15.126] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[22:18:15.126] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[22:18:15.127] Buildbucket request:
{
"requestId": "8901487417799370896",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "c52d8c9dd10585a7cb325559cf6a0627b3bb80ca",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8901487417799370896"
},
{
"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:18:16.279] Scheduled build:
{
"id": "8736057355948196945",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 9542,
"createdBy": "project:chromium",
"createTime": "2024-09-22T22:18:15.188412321Z",
"updateTime": "2024-09-22T22:18:15.188412321Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "c52d8c9dd10585a7cb325559cf6a0627b3bb80ca",
"ref": "refs/heads/main"
}
},
"canary": true
}
[22:18:16.279] Task URL: https://cr-buildbucket-dev.appspot.com/build/8736057355948196945
[22:18:16.279] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:2:0) after 6m27s
[22:18:17.688] Received PubSub notification, asking Buildbucket for the build status
[22:18:17.712] Build status: SCHEDULED
[22:19:19.629] Received PubSub notification, asking Buildbucket for the build status
[22:19:19.781] Build status: STARTED
[22:24:43.298] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:2:0)
[22:24:43.333] Build status: STARTED
[22:24:43.333] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:5:0) after 1m4s
[22:25:47.348] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:5:0)
[22:25:47.372] Build status: STARTED
[22:25:47.372] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:6:0) after 2m33s
[22:28:20.387] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:6:0)
[22:28:20.447] Build status: STARTED
[22:28:20.447] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:7:0) after 6m44s
[22:35:04.464] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:7:0)
[22:35:04.580] Build status: STARTED
[22:35:04.580] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:8:0) after 4m6s
[22:39:10.603] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:8:0)
[22:39:10.648] Build status: STARTED
[22:39:10.648] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:9:0) after 6m37s
[22:45:47.664] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:9:0)
[22:45:47.728] Build status: STARTED
[22:45:47.728] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:10:0) after 2m38s
[22:48:25.746] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:10:0)
[22:48:25.770] Build status: STARTED
[22:48:25.770] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:11:0) after 4m43s
[22:53:08.789] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:11:0)
[22:53:08.835] Build status: STARTED
[22:53:08.835] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:12:0) after 8m13s
[23:01:21.853] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:12:0)
[23:01:21.897] Build status: STARTED
[23:01:21.897] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:13:0) after 3m37s
[23:04:58.913] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:13:0)
[23:04:58.939] Build status: STARTED
[23:04:58.939] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:14:0) after 3m14s
[23:08:12.958] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:14:0)
[23:08:13.003] Build status: STARTED
[23:08:13.003] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:15:0) after 3m12s
[23:11:25.021] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:15:0)
[23:11:25.077] Build status: STARTED
[23:11:25.077] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901487417799370896:16:0) after 9m44s
[23:13:54.854] Received PubSub notification, asking Buildbucket for the build status
[23:13:54.876] Build:
{
"id": "8736057355948196945",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 9542,
"createdBy": "project:chromium",
"createTime": "2024-09-22T22:18:15.188412321Z",
"startTime": "2024-09-22T22:19:18.067711917Z",
"endTime": "2024-09-22T23:13:54.381684912Z",
"updateTime": "2024-09-22T23:13:54.381684912Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "c52d8c9dd10585a7cb325559cf6a0627b3bb80ca",
"ref": "refs/heads/main"
}
},
"canary": true
}
[23:13:54.876] Invocation finished in 55m40.83631837s with status SUCCEEDED