[22:25:56.059] New invocation is queued and will start shortly
[22:25:57.127] Starting the invocation (attempt 1)
[22:25:57.154] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/8043b2e09f5ae983d815ed528661d78eeb5d9020"
[22:25:57.154] Popped gitiles commit info from properties and tags
[22:25:57.154] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[22:25:57.154] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[22:25:57.154] Buildbucket request:
{
"requestId": "8917431999428872416",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "8043b2e09f5ae983d815ed528661d78eeb5d9020",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8917431999428872416"
},
{
"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:25:58.831] Scheduled build:
{
"id": "8752001937413766897",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 6845,
"createdBy": "project:chromium",
"createTime": "2024-03-30T22:25:57.358373522Z",
"updateTime": "2024-03-30T22:25:57.358373522Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "8043b2e09f5ae983d815ed528661d78eeb5d9020",
"ref": "refs/heads/main"
}
},
"canary": true
}
[22:25:58.831] Task URL: https://cr-buildbucket-dev.appspot.com/build/8752001937413766897
[22:25:58.831] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:2:0) after 3m19s
[22:25:59.846] Received PubSub notification, asking Buildbucket for the build status
[22:25:59.886] Build status: SCHEDULED
[22:26:06.450] Received PubSub notification, asking Buildbucket for the build status
[22:26:06.541] Build status: STARTED
[22:29:17.848] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:2:0)
[22:29:17.959] Build status: STARTED
[22:29:17.959] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:5:0) after 3m40s
[22:32:57.988] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:5:0)
[22:32:58.024] Build status: STARTED
[22:32:58.024] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:6:0) after 4m59s
[22:37:57.042] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:6:0)
[22:37:57.103] Build status: STARTED
[22:37:57.103] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:7:0) after 5m11s
[22:43:08.120] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:7:0)
[22:43:08.172] Build status: STARTED
[22:43:08.172] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:8:0) after 2m4s
[22:45:12.191] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:8:0)
[22:45:12.243] Build status: STARTED
[22:45:12.243] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:9:0) after 5m55s
[22:51:07.272] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:9:0)
[22:51:07.323] Build status: STARTED
[22:51:07.323] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:10:0) after 5m24s
[22:56:31.361] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:10:0)
[22:56:31.408] Build status: STARTED
[22:56:31.408] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:11:0) after 1m42s
[22:58:13.425] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:11:0)
[22:58:13.512] Build status: STARTED
[22:58:13.512] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:12:0) after 4m54s
[23:03:07.531] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:12:0)
[23:03:07.585] Build status: STARTED
[23:03:07.585] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:13:0) after 1m49s
[23:04:56.603] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:13:0)
[23:04:56.712] Build status: STARTED
[23:04:56.712] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:14:0) after 3m32s
[23:08:28.738] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:14:0)
[23:08:28.780] Build status: STARTED
[23:08:28.780] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:15:0) after 3m18s
[23:11:46.806] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:15:0)
[23:11:46.838] Build status: STARTED
[23:11:46.838] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8917431999428872416:16:0) after 7m19s
[23:18:41.776] Received PubSub notification, asking Buildbucket for the build status
[23:18:41.889] Build:
{
"id": "8752001937413766897",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 6845,
"createdBy": "project:chromium",
"createTime": "2024-03-30T22:25:57.358373522Z",
"startTime": "2024-03-30T22:26:06.118321251Z",
"endTime": "2024-03-30T23:18:40.325869245Z",
"updateTime": "2024-03-30T23:18:40.325869245Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "8043b2e09f5ae983d815ed528661d78eeb5d9020",
"ref": "refs/heads/main"
}
},
"canary": true
}
[23:18:41.889] Invocation finished in 52m45.835932457s with status SUCCEEDED