[18:51:35.065] New invocation is queued and will start shortly
[18:51:36.168] Starting the invocation (attempt 1)
[18:51:36.197] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/a5ef13fdb0138d4718cc0010b5798ec7fc753001"
[18:51:36.198] Popped gitiles commit info from properties and tags
[18:51:36.198] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[18:51:36.198] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[18:51:36.198] Buildbucket request:
{
"requestId": "8874683717017091696",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "a5ef13fdb0138d4718cc0010b5798ec7fc753001",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8874683717017091696"
},
{
"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"
}
}
[18:51:36.922] Scheduled build:
{
"id": "8709253655108850305",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 18967,
"createdBy": "project:chromium",
"createTime": "2025-07-15T18:51:36.263802869Z",
"updateTime": "2025-07-15T18:51:36.263802869Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "a5ef13fdb0138d4718cc0010b5798ec7fc753001",
"ref": "refs/heads/main"
}
},
"canary": true
}
[18:51:36.922] Task URL: https://cr-buildbucket-dev.appspot.com/build/8709253655108850305
[18:51:36.922] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:2:0) after 8m4s
[18:51:42.480] Received PubSub notification, asking Buildbucket for the build status
[18:51:42.518] Build status: SCHEDULED
[18:59:40.950] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:2:0)
[18:59:41.014] Build status: SCHEDULED
[18:59:41.014] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:4:0) after 8m8s
[19:07:49.036] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:4:0)
[19:07:49.072] Build status: SCHEDULED
[19:07:49.072] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:5:0) after 7m6s
[19:14:55.092] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:5:0)
[19:14:55.123] Build status: SCHEDULED
[19:14:55.123] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:6:0) after 2m28s
[19:17:23.143] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:6:0)
[19:17:23.164] Build status: SCHEDULED
[19:17:23.165] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:7:0) after 1m5s
[19:18:28.195] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:7:0)
[19:18:28.223] Build status: SCHEDULED
[19:18:28.223] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:8:0) after 5m9s
[19:23:37.246] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:8:0)
[19:23:37.293] Build status: SCHEDULED
[19:23:37.293] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:9:0) after 1m19s
[19:24:56.434] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:9:0)
[19:24:56.463] Build status: SCHEDULED
[19:24:56.463] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:10:0) after 4m47s
[19:29:43.489] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:10:0)
[19:29:43.520] Build status: SCHEDULED
[19:29:43.520] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:11:0) after 7m35s
[19:37:18.543] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:11:0)
[19:37:18.573] Build status: SCHEDULED
[19:37:18.573] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:12:0) after 9m54s
[19:38:27.195] Received PubSub notification, asking Buildbucket for the build status
[19:38:27.228] Build status: STARTED
[19:47:12.597] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:12:0)
[19:47:12.629] Build status: STARTED
[19:47:12.629] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:14:0) after 5m19s
[19:52:31.651] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:14:0)
[19:52:31.688] Build status: STARTED
[19:52:31.688] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:15:0) after 8m17s
[20:00:48.710] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:15:0)
[20:00:48.742] Build status: STARTED
[20:00:48.742] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:16:0) after 1m21s
[20:02:09.765] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:16:0)
[20:02:09.799] Build status: STARTED
[20:02:09.799] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:17:0) after 5m5s
[20:07:14.821] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:17:0)
[20:07:14.853] Build status: STARTED
[20:07:14.853] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:18:0) after 9m52s
[20:17:06.883] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:18:0)
[20:17:06.972] Build status: STARTED
[20:17:06.972] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:19:0) after 8m12s
[20:25:19.007] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:19:0)
[20:25:19.038] Build status: STARTED
[20:25:19.038] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:20:0) after 4m18s
[20:29:37.060] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:20:0)
[20:29:37.097] Build status: STARTED
[20:29:37.097] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:21:0) after 2m34s
[20:32:11.126] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:21:0)
[20:32:11.166] Build status: STARTED
[20:32:11.166] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:22:0) after 5m49s
[20:38:00.189] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:22:0)
[20:38:00.219] Build status: STARTED
[20:38:00.219] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:23:0) after 3m13s
[20:41:13.243] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:23:0)
[20:41:13.279] Build status: STARTED
[20:41:13.279] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:24:0) after 3m44s
[20:44:58.627] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:24:0)
[20:44:58.659] Build status: STARTED
[20:44:58.659] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:25:0) after 7m35s
[20:52:33.678] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:25:0)
[20:52:33.705] Build status: STARTED
[20:52:33.705] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:26:0) after 9m45s
[21:02:18.714] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:26:0)
[21:02:18.793] Build status: STARTED
[21:02:18.793] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:27:0) after 5m28s
[21:07:46.820] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:27:0)
[21:07:46.838] Build status: STARTED
[21:07:46.838] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:28:0) after 8m38s
[21:16:24.862] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:28:0)
[21:16:24.894] Build status: STARTED
[21:16:24.895] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:29:0) after 3m4s
[21:19:28.921] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:29:0)
[21:19:28.953] Build status: STARTED
[21:19:28.953] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:30:0) after 9m2s
[21:28:30.976] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:30:0)
[21:28:31.007] Build status: STARTED
[21:28:31.007] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8874683717017091696:31:0) after 7m56s
[21:32:53.316] Received PubSub notification, asking Buildbucket for the build status
[21:32:53.349] Build:
{
"id": "8709253655108850305",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 18967,
"createdBy": "project:chromium",
"createTime": "2025-07-15T18:51:36.263802869Z",
"startTime": "2025-07-15T19:38:26.900573622Z",
"endTime": "2025-07-15T21:32:52.950589165Z",
"updateTime": "2025-07-15T21:32:52.950589165Z",
"status": "FAILURE",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "a5ef13fdb0138d4718cc0010b5798ec7fc753001",
"ref": "refs/heads/main"
}
},
"canary": true
}
[21:32:53.349] Invocation finished in 2h41m18.28936267s with status FAILED