[23:46:36.076] New invocation is queued and will start shortly
[23:46:37.150] Starting the invocation (attempt 1)
[23:46:37.179] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/a6bbb88532c7a55fb26aa9e1144a72f8211174c3"
[23:46:37.179] Popped gitiles commit info from properties and tags
[23:46:37.179] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[23:46:37.179] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[23:46:37.179] Buildbucket request:
{
"requestId": "8914346627449821968",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "a6bbb88532c7a55fb26aa9e1144a72f8211174c3",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8914346627449821968"
},
{
"key": "scheduler_job_id",
"value": "chromium/win-local-ssd-rel-dev"
},
{
"key": "user_agent",
"value": "luci-scheduler-dev"
}
],
"notify": {
"pubsubTopic": "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
}
}
[23:46:38.408] Scheduled build:
{
"id": "8748916565534300833",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 11223,
"createdBy": "project:chromium",
"createTime": "2024-05-03T23:46:37.276111304Z",
"updateTime": "2024-05-03T23:46:37.276111304Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "a6bbb88532c7a55fb26aa9e1144a72f8211174c3",
"ref": "refs/heads/main"
}
},
"canary": true
}
[23:46:38.408] Task URL: https://cr-buildbucket-dev.appspot.com/build/8748916565534300833
[23:46:38.408] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:2:0) after 6m45s
[23:46:39.202] Received PubSub notification, asking Buildbucket for the build status
[23:46:39.229] Build status: SCHEDULED
[23:47:41.590] Received PubSub notification, asking Buildbucket for the build status
[23:47:41.636] Build status: STARTED
[23:53:23.431] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:2:0)
[23:53:23.477] Build status: STARTED
[23:53:23.477] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:5:0) after 5m27s
[23:58:50.502] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:5:0)
[23:58:50.541] Build status: STARTED
[23:58:50.541] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:6:0) after 6m40s
[00:05:30.561] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:6:0)
[00:05:30.605] Build status: STARTED
[00:05:30.605] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:7:0) after 4m22s
[00:09:52.625] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:7:0)
[00:09:52.665] Build status: STARTED
[00:09:52.665] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:8:0) after 2m20s
[00:12:12.685] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:8:0)
[00:12:12.721] Build status: STARTED
[00:12:12.721] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:9:0) after 1m42s
[00:13:54.736] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:9:0)
[00:13:54.772] Build status: STARTED
[00:13:54.772] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:10:0) after 1m40s
[00:15:34.789] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:10:0)
[00:15:34.826] Build status: STARTED
[00:15:34.826] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:11:0) after 2m22s
[00:17:56.849] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:11:0)
[00:17:56.883] Build status: STARTED
[00:17:56.883] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:12:0) after 7m48s
[00:25:44.903] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:12:0)
[00:25:44.960] Build status: STARTED
[00:25:44.960] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:13:0) after 1m55s
[00:27:39.983] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:13:0)
[00:27:40.013] Build status: STARTED
[00:27:40.013] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:14:0) after 9m6s
[00:36:46.033] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:14:0)
[00:36:46.150] Build status: STARTED
[00:36:46.150] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914346627449821968:15:0) after 5m47s
[00:37:50.083] Received PubSub notification, asking Buildbucket for the build status
[00:37:50.159] Build:
{
"id": "8748916565534300833",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 11223,
"createdBy": "project:chromium",
"createTime": "2024-05-03T23:46:37.276111304Z",
"startTime": "2024-05-03T23:47:41.296725398Z",
"endTime": "2024-05-04T00:37:49.472057050Z",
"updateTime": "2024-05-04T00:37:49.472057050Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "a6bbb88532c7a55fb26aa9e1144a72f8211174c3",
"ref": "refs/heads/main"
}
},
"canary": true
}
[00:37:50.159] Invocation finished in 51m14.093132105s with status SUCCEEDED