[19:03:34.039] New invocation is queued and will start shortly
[19:03:35.099] Starting the invocation (attempt 1)
[19:03:35.123] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/4f39aaf342c2d79e1526798f3be12f365f08af64"
[19:03:35.123] Popped gitiles commit info from properties and tags
[19:03:35.123] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[19:03:35.125] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[19:03:35.125] Buildbucket request:
{
"requestId": "8902858619669706592",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "4f39aaf342c2d79e1526798f3be12f365f08af64",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8902858619669706592"
},
{
"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"
}
}
[19:03:35.860] Scheduled build:
{
"id": "8737428557812852257",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 14484,
"createdBy": "project:chromium",
"createTime": "2024-09-07T19:03:35.187690769Z",
"updateTime": "2024-09-07T19:03:35.187690769Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "4f39aaf342c2d79e1526798f3be12f365f08af64",
"ref": "refs/heads/main"
}
},
"canary": true
}
[19:03:35.860] Task URL: https://cr-buildbucket-dev.appspot.com/build/8737428557812852257
[19:03:35.860] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:2:0) after 1m42s
[19:03:36.783] Received PubSub notification, asking Buildbucket for the build status
[19:03:36.809] Build status: SCHEDULED
[19:04:46.624] Received PubSub notification, asking Buildbucket for the build status
[19:04:46.652] Build status: STARTED
[19:05:17.879] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:2:0)
[19:05:17.899] Build status: STARTED
[19:05:17.899] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:5:0) after 6m54s
[19:12:11.915] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:5:0)
[19:12:11.950] Build status: STARTED
[19:12:11.950] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:6:0) after 6m8s
[19:18:19.969] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:6:0)
[19:18:19.992] Build status: STARTED
[19:18:19.992] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:7:0) after 1m4s
[19:19:24.013] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:7:0)
[19:19:24.075] Build status: STARTED
[19:19:24.075] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:8:0) after 4m12s
[19:23:36.092] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:8:0)
[19:23:36.117] Build status: STARTED
[19:23:36.117] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:9:0) after 4m38s
[19:28:14.133] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:9:0)
[19:28:14.149] Build status: STARTED
[19:28:14.149] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:10:0) after 2m11s
[19:30:25.164] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:10:0)
[19:30:25.199] Build status: STARTED
[19:30:25.199] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:11:0) after 7m11s
[19:37:36.213] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:11:0)
[19:37:36.244] Build status: STARTED
[19:37:36.244] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:12:0) after 8m40s
[19:46:16.279] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:12:0)
[19:46:16.312] Build status: STARTED
[19:46:16.312] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:13:0) after 9m6s
[19:55:22.337] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:13:0)
[19:55:22.366] Build status: STARTED
[19:55:22.366] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:14:0) after 6m31s
[20:01:53.382] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:14:0)
[20:01:53.415] Build status: STARTED
[20:01:53.415] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:15:0) after 2m42s
[20:04:35.531] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:15:0)
[20:04:35.568] Build status: STARTED
[20:04:35.568] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:16:0) after 6m13s
[20:10:48.584] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:16:0)
[20:10:48.630] Build status: STARTED
[20:10:48.630] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:17:0) after 1m45s
[20:12:33.660] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:17:0)
[20:12:33.711] Build status: STARTED
[20:12:33.711] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:18:0) after 9m43s
[20:22:16.729] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:18:0)
[20:22:16.751] Build status: STARTED
[20:22:16.751] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:19:0) after 8m57s
[20:31:13.767] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:19:0)
[20:31:13.804] Build status: STARTED
[20:31:13.804] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:20:0) after 4m13s
[20:35:26.823] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:20:0)
[20:35:26.867] Build status: STARTED
[20:35:26.867] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:21:0) after 5m52s
[20:41:18.884] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:21:0)
[20:41:18.934] Build status: STARTED
[20:41:18.934] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:22:0) after 4m8s
[20:45:26.951] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:22:0)
[20:45:26.984] Build status: STARTED
[20:45:26.984] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:23:0) after 5m48s
[20:51:15.026] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:23:0)
[20:51:15.071] Build status: STARTED
[20:51:15.071] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:24:0) after 1m25s
[20:52:40.086] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:24:0)
[20:52:40.115] Build status: STARTED
[20:52:40.115] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:25:0) after 1m34s
[20:54:14.138] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:25:0)
[20:54:14.172] Build status: STARTED
[20:54:14.172] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:26:0) after 9m28s
[21:03:42.189] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:26:0)
[21:03:42.219] Build status: STARTED
[21:03:42.219] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:27:0) after 5m10s
[21:08:52.249] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:27:0)
[21:08:52.287] Build status: STARTED
[21:08:52.287] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:28:0) after 2m15s
[21:11:07.308] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:28:0)
[21:11:07.369] Build status: STARTED
[21:11:07.370] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8902858619669706592:29:0) after 2m2s
[21:12:38.852] Received PubSub notification, asking Buildbucket for the build status
[21:12:38.880] Build:
{
"id": "8737428557812852257",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 14484,
"createdBy": "project:chromium",
"createTime": "2024-09-07T19:03:35.187690769Z",
"startTime": "2024-09-07T19:04:46.379594690Z",
"endTime": "2024-09-07T21:12:38.367683291Z",
"updateTime": "2024-09-07T21:12:38.367683291Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "4f39aaf342c2d79e1526798f3be12f365f08af64",
"ref": "refs/heads/main"
}
},
"canary": true
}
[21:12:38.880] Invocation finished in 2h9m4.846691637s with status SUCCEEDED