[09:31:26.102] New invocation is queued and will start shortly
[09:31:27.213] Starting the invocation (attempt 1)
[09:31:27.243] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/cfddd11ed368490553618e6c4e56562eeeae6299"
[09:31:27.243] Popped gitiles commit info from properties and tags
[09:31:27.243] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[09:31:27.248] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[09:31:27.248] Buildbucket request:
{
"requestId": "8922282365930770512",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "cfddd11ed368490553618e6c4e56562eeeae6299",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8922282365930770512"
},
{
"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"
}
}
[09:31:28.369] Scheduled build:
{
"id": "8756852303850704721",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 7627,
"createdBy": "project:chromium",
"createTime": "2024-02-06T09:31:27.462460076Z",
"updateTime": "2024-02-06T09:31:27.462460076Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "cfddd11ed368490553618e6c4e56562eeeae6299",
"ref": "refs/heads/main"
}
},
"canary": true
}
[09:31:28.369] Task URL: https://cr-buildbucket-dev.appspot.com/build/8756852303850704721
[09:31:28.369] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:2:0) after 9m25s
[09:31:29.198] Received PubSub notification, asking Buildbucket for the build status
[09:31:29.243] Build status: SCHEDULED
[09:40:53.389] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:2:0)
[09:40:53.420] Build status: SCHEDULED
[09:40:53.420] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:4:0) after 3m34s
[09:44:27.436] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:4:0)
[09:44:27.666] Build status: SCHEDULED
[09:44:27.666] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:5:0) after 9m20s
[09:49:18.482] Received PubSub notification, asking Buildbucket for the build status
[09:49:18.507] Build status: STARTED
[09:53:47.684] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:5:0)
[09:53:47.736] Build status: STARTED
[09:53:47.736] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:7:0) after 8m5s
[10:01:52.766] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:7:0)
[10:01:52.798] Build status: STARTED
[10:01:52.798] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:8:0) after 2m27s
[10:04:19.818] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:8:0)
[10:04:19.865] Build status: STARTED
[10:04:19.865] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:9:0) after 1m7s
[10:05:26.886] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:9:0)
[10:05:27.002] Build status: STARTED
[10:05:27.002] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:10:0) after 1m32s
[10:06:59.625] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:10:0)
[10:06:59.652] Build status: STARTED
[10:06:59.652] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:11:0) after 2m17s
[10:09:16.669] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:11:0)
[10:09:16.724] Build status: STARTED
[10:09:16.724] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:12:0) after 2m27s
[10:11:44.176] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:12:0)
[10:11:44.206] Build status: STARTED
[10:11:44.206] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:13:0) after 1m23s
[10:13:07.228] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:13:0)
[10:13:07.287] Build status: STARTED
[10:13:07.287] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:14:0) after 5m33s
[10:18:40.303] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:14:0)
[10:18:40.365] Build status: STARTED
[10:18:40.365] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8922282365930770512:15:0) after 3m18s
[10:19:50.583] Received PubSub notification, asking Buildbucket for the build status
[10:19:50.606] Build:
{
"id": "8756852303850704721",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 7627,
"createdBy": "project:chromium",
"createTime": "2024-02-06T09:31:27.462460076Z",
"startTime": "2024-02-06T09:49:10.438447178Z",
"endTime": "2024-02-06T10:19:49.245479822Z",
"updateTime": "2024-02-06T10:19:49.245479822Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "cfddd11ed368490553618e6c4e56562eeeae6299",
"ref": "refs/heads/main"
}
},
"canary": true
}
[10:19:50.606] Invocation finished in 48m24.511142795s with status SUCCEEDED