[07:34:39.039] New invocation is queued and will start shortly
[07:34:40.105] Starting the invocation (attempt 1)
[07:34:40.129] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/42dc65be7adaa8ab839b28c853fd155b1dc9d424"
[07:34:40.129] Popped gitiles commit info from properties and tags
[07:34:40.129] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[07:34:40.130] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[07:34:40.131] Buildbucket request:
{
"requestId": "8883786002645161648",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "42dc65be7adaa8ab839b28c853fd155b1dc9d424",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8883786002645161648"
},
{
"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"
}
}
[07:34:40.827] Scheduled build:
{
"id": "8718355940795684865",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 17145,
"createdBy": "project:chromium",
"createTime": "2025-04-06T07:34:40.183055926Z",
"updateTime": "2025-04-06T07:34:40.183055926Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "42dc65be7adaa8ab839b28c853fd155b1dc9d424",
"ref": "refs/heads/main"
}
},
"canary": true
}
[07:34:40.827] Task URL: https://cr-buildbucket-dev.appspot.com/build/8718355940795684865
[07:34:40.827] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:2:0) after 5m54s
[07:34:41.333] Received PubSub notification, asking Buildbucket for the build status
[07:34:41.365] Build status: SCHEDULED
[07:34:47.324] Received PubSub notification, asking Buildbucket for the build status
[07:34:47.355] Build status: STARTED
[07:40:34.841] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:2:0)
[07:40:34.869] Build status: STARTED
[07:40:34.869] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:5:0) after 3m29s
[07:44:03.889] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:5:0)
[07:44:03.923] Build status: STARTED
[07:44:03.923] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:6:0) after 8m51s
[07:52:54.940] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:6:0)
[07:52:54.999] Build status: STARTED
[07:52:54.999] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:7:0) after 9m13s
[08:02:08.014] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:7:0)
[08:02:08.045] Build status: STARTED
[08:02:08.045] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:8:0) after 9m51s
[08:11:59.061] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:8:0)
[08:11:59.079] Build status: STARTED
[08:11:59.079] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:9:0) after 6m15s
[08:18:14.093] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:9:0)
[08:18:14.122] Build status: STARTED
[08:18:14.122] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:10:0) after 2m22s
[08:20:36.141] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:10:0)
[08:20:36.176] Build status: STARTED
[08:20:36.176] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:11:0) after 4m37s
[08:25:13.191] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:11:0)
[08:25:13.218] Build status: STARTED
[08:25:13.218] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:12:0) after 1m9s
[08:26:22.230] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:12:0)
[08:26:22.299] Build status: STARTED
[08:26:22.299] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:13:0) after 5m30s
[08:31:52.346] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:13:0)
[08:31:52.391] Build status: STARTED
[08:31:52.391] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:14:0) after 3m12s
[08:35:04.406] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:14:0)
[08:35:04.436] Build status: STARTED
[08:35:04.436] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:15:0) after 8m9s
[08:43:13.452] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:15:0)
[08:43:13.469] Build status: STARTED
[08:43:13.470] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8883786002645161648:16:0) after 7m3s
[08:44:45.878] Received PubSub notification, asking Buildbucket for the build status
[08:44:45.919] Build:
{
"id": "8718355940795684865",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 17145,
"createdBy": "project:chromium",
"createTime": "2025-04-06T07:34:40.183055926Z",
"startTime": "2025-04-06T07:34:47.137609347Z",
"endTime": "2025-04-06T08:44:45.584899124Z",
"updateTime": "2025-04-06T08:44:45.584899124Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "42dc65be7adaa8ab839b28c853fd155b1dc9d424",
"ref": "refs/heads/main"
}
},
"canary": true
}
[08:44:45.919] Invocation finished in 1h10m6.884660767s with status SUCCEEDED