[11:54:19.048] New invocation is queued and will start shortly
[11:54:20.133] Starting the invocation (attempt 1)
[11:54:20.165] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/b0161f36141630fd6a4c7d60f15ce995b66cc843"
[11:54:20.165] Popped gitiles commit info from properties and tags
[11:54:20.165] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[11:54:20.165] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[11:54:20.165] Buildbucket request:
{
"requestId": "8909227413383361936",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "b0161f36141630fd6a4c7d60f15ce995b66cc843",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8909227413383361936"
},
{
"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"
}
}
[11:54:21.288] Scheduled build:
{
"id": "8743797351481896193",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 8324,
"createdBy": "project:chromium",
"createTime": "2024-06-29T11:54:20.238739657Z",
"updateTime": "2024-06-29T11:54:20.238739657Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "b0161f36141630fd6a4c7d60f15ce995b66cc843",
"ref": "refs/heads/main"
}
},
"canary": true
}
[11:54:21.288] Task URL: https://cr-buildbucket-dev.appspot.com/build/8743797351481896193
[11:54:21.288] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:2:0) after 9m57s
[11:54:22.129] Received PubSub notification, asking Buildbucket for the build status
[11:54:22.154] Build status: SCHEDULED
[11:59:03.641] Received PubSub notification, asking Buildbucket for the build status
[11:59:03.696] Build status: STARTED
[12:04:18.305] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:2:0)
[12:04:18.367] Build status: STARTED
[12:04:18.368] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:5:0) after 9m14s
[12:13:32.387] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:5:0)
[12:13:32.425] Build status: STARTED
[12:13:32.425] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:6:0) after 8m51s
[12:22:23.444] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:6:0)
[12:22:23.472] Build status: STARTED
[12:22:23.472] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:7:0) after 9m10s
[12:31:33.491] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:7:0)
[12:31:33.564] Build status: STARTED
[12:31:33.564] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:8:0) after 7m47s
[12:39:20.580] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:8:0)
[12:39:20.610] Build status: STARTED
[12:39:20.610] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:9:0) after 9m37s
[12:48:57.627] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:9:0)
[12:48:57.662] Build status: STARTED
[12:48:57.662] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:10:0) after 1m6s
[12:50:03.688] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:10:0)
[12:50:03.732] Build status: STARTED
[12:50:03.732] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:11:0) after 4m47s
[12:54:51.144] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:11:0)
[12:54:51.175] Build status: STARTED
[12:54:51.175] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:12:0) after 2m28s
[12:57:19.192] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:12:0)
[12:57:19.255] Build status: STARTED
[12:57:19.255] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:13:0) after 6m29s
[13:03:48.270] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:13:0)
[13:03:48.312] Build status: STARTED
[13:03:48.312] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:14:0) after 7m6s
[13:10:54.327] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:14:0)
[13:10:54.366] Build status: STARTED
[13:10:54.367] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:15:0) after 9m57s
[13:20:51.392] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:15:0)
[13:20:51.423] Build status: STARTED
[13:20:51.424] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8909227413383361936:16:0) after 5m23s
[13:21:30.691] Received PubSub notification, asking Buildbucket for the build status
[13:21:30.725] Build:
{
"id": "8743797351481896193",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 8324,
"createdBy": "project:chromium",
"createTime": "2024-06-29T11:54:20.238739657Z",
"startTime": "2024-06-29T11:59:03.329088350Z",
"endTime": "2024-06-29T13:21:29.235682282Z",
"updateTime": "2024-06-29T13:21:29.235682282Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "b0161f36141630fd6a4c7d60f15ce995b66cc843",
"ref": "refs/heads/main"
}
},
"canary": true
}
[13:21:30.725] Invocation finished in 1h27m11.683987925s with status SUCCEEDED