[10:29:08.045] New invocation is queued and will start shortly
[10:29:09.113] Starting the invocation (attempt 1)
[10:29:09.139] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/5c9800f3aa395dfdfa761c50c62204001552fb92"
[10:29:09.139] Popped gitiles commit info from properties and tags
[10:29:09.139] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[10:29:09.139] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[10:29:09.139] Buildbucket request:
{
"requestId": "8882778458469060128",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5c9800f3aa395dfdfa761c50c62204001552fb92",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8882778458469060128"
},
{
"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"
}
}
[10:29:09.821] Scheduled build:
{
"id": "8717348396613115921",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 24280,
"createdBy": "project:chromium",
"createTime": "2025-04-17T10:29:09.192431154Z",
"updateTime": "2025-04-17T10:29:09.192431154Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5c9800f3aa395dfdfa761c50c62204001552fb92",
"ref": "refs/heads/main"
}
},
"canary": true
}
[10:29:09.821] Task URL: https://cr-buildbucket-dev.appspot.com/build/8717348396613115921
[10:29:09.821] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:2:0) after 1m9s
[10:29:10.580] Received PubSub notification, asking Buildbucket for the build status
[10:29:10.597] Build status: SCHEDULED
[10:30:18.838] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:2:0)
[10:30:18.869] Build status: SCHEDULED
[10:30:18.869] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:4:0) after 2m33s
[10:32:51.886] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:4:0)
[10:32:51.931] Build status: SCHEDULED
[10:32:51.931] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:5:0) after 2m10s
[10:35:01.945] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:5:0)
[10:35:01.976] Build status: SCHEDULED
[10:35:01.976] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:6:0) after 4m31s
[10:38:44.554] Received PubSub notification, asking Buildbucket for the build status
[10:38:44.584] Build status: STARTED
[10:39:32.995] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:6:0)
[10:39:33.027] Build status: STARTED
[10:39:33.027] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:8:0) after 3m14s
[10:42:47.045] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:8:0)
[10:42:47.112] Build status: STARTED
[10:42:47.112] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:9:0) after 2m4s
[10:44:51.127] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:9:0)
[10:44:51.162] Build status: STARTED
[10:44:51.162] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:10:0) after 3m44s
[10:48:35.177] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:10:0)
[10:48:35.209] Build status: STARTED
[10:48:35.209] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:11:0) after 2m40s
[10:51:15.224] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:11:0)
[10:51:15.243] Build status: STARTED
[10:51:15.243] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:12:0) after 1m12s
[10:52:27.260] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:12:0)
[10:52:27.301] Build status: STARTED
[10:52:27.301] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:13:0) after 2m9s
[10:54:36.326] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:13:0)
[10:54:36.370] Build status: STARTED
[10:54:36.370] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:14:0) after 5m28s
[11:00:04.401] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:14:0)
[11:00:04.420] Build status: STARTED
[11:00:04.420] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:15:0) after 6m43s
[11:06:47.438] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:15:0)
[11:06:47.475] Build status: STARTED
[11:06:47.475] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:16:0) after 9m30s
[11:16:17.492] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:16:0)
[11:16:17.517] Build status: STARTED
[11:16:17.517] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:17:0) after 2m13s
[11:18:30.534] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:17:0)
[11:18:30.590] Build status: STARTED
[11:18:30.590] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:18:0) after 3m54s
[11:22:24.683] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:18:0)
[11:22:24.705] Build status: STARTED
[11:22:24.705] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:19:0) after 7m33s
[11:29:57.722] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:19:0)
[11:29:57.758] Build status: STARTED
[11:29:57.758] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:20:0) after 2m17s
[11:32:14.781] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:20:0)
[11:32:14.811] Build status: STARTED
[11:32:14.811] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:21:0) after 8m22s
[11:40:36.832] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:21:0)
[11:40:36.900] Build status: STARTED
[11:40:36.900] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:22:0) after 4m8s
[11:44:44.921] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:22:0)
[11:44:45.073] Build status: STARTED
[11:44:45.073] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:23:0) after 2m26s
[11:47:11.091] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:23:0)
[11:47:11.119] Build status: STARTED
[11:47:11.119] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:24:0) after 9m5s
[11:56:16.135] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:24:0)
[11:56:16.165] Build status: STARTED
[11:56:16.165] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:25:0) after 9m44s
[12:06:00.185] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:25:0)
[12:06:00.228] Build status: STARTED
[12:06:00.228] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:26:0) after 3m12s
[12:09:12.244] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:26:0)
[12:09:12.276] Build status: STARTED
[12:09:12.276] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:27:0) after 4m40s
[12:13:52.294] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:27:0)
[12:13:52.326] Build status: STARTED
[12:13:52.326] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:28:0) after 1m30s
[12:15:22.344] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:28:0)
[12:15:22.381] Build status: STARTED
[12:15:22.381] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8882778458469060128:29:0) after 8m3s
[12:19:47.383] Received PubSub notification, asking Buildbucket for the build status
[12:19:48.128] Build:
{
"id": "8717348396613115921",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 24280,
"createdBy": "project:chromium",
"createTime": "2025-04-17T10:29:09.192431154Z",
"startTime": "2025-04-17T10:38:44.293523466Z",
"endTime": "2025-04-17T12:19:46.393382250Z",
"updateTime": "2025-04-17T12:19:46.393382250Z",
"status": "FAILURE",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5c9800f3aa395dfdfa761c50c62204001552fb92",
"ref": "refs/heads/main"
}
},
"canary": true
}
[12:19:48.128] Invocation finished in 1h50m40.088531124s with status FAILED