[22:05:40.059] New invocation is queued and will start shortly
[22:05:41.122] Starting the invocation (attempt 1)
[22:05:41.148] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/120a605a38ab3085de9bc66c79e29f592f50c332"
[22:05:41.148] Popped gitiles commit info from properties and tags
[22:05:41.148] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[22:05:41.148] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[22:05:41.148] Buildbucket request:
{
"requestId": "8941079082728897536",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "120a605a38ab3085de9bc66c79e29f592f50c332",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8941079082728897536"
},
{
"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"
}
}
[22:05:42.318] Scheduled build:
{
"id": "8775649020773944145",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 1518,
"createdBy": "project:chromium",
"createTime": "2023-07-13T22:05:41.300518500Z",
"updateTime": "2023-07-13T22:05:41.300518500Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "120a605a38ab3085de9bc66c79e29f592f50c332",
"ref": "refs/heads/main"
}
}
}
[22:05:42.318] Task URL: https://cr-buildbucket-dev.appspot.com/build/8775649020773944145
[22:05:42.318] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:2:0) after 6m43s
[22:05:43.179] Received PubSub notification, asking Buildbucket for the build status
[22:05:43.204] Build status: SCHEDULED
[22:12:25.346] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:2:0)
[22:12:25.375] Build status: SCHEDULED
[22:12:25.375] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:4:0) after 3m35s
[22:16:00.399] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:4:0)
[22:16:00.457] Build status: SCHEDULED
[22:16:00.457] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:5:0) after 4m38s
[22:20:38.480] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:5:0)
[22:20:38.510] Build status: SCHEDULED
[22:20:38.510] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:6:0) after 4m20s
[22:24:58.529] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:6:0)
[22:24:58.553] Build status: SCHEDULED
[22:24:58.553] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:7:0) after 2m1s
[22:27:00.257] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:7:0)
[22:27:00.304] Build status: SCHEDULED
[22:27:00.304] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:8:0) after 6m15s
[22:33:15.324] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:8:0)
[22:33:15.351] Build status: SCHEDULED
[22:33:15.351] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:9:0) after 2m43s
[22:35:58.372] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:9:0)
[22:35:58.399] Build status: SCHEDULED
[22:35:58.399] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:10:0) after 8m41s
[22:42:16.285] Received PubSub notification, asking Buildbucket for the build status
[22:42:16.309] Build status: STARTED
[22:44:39.417] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:10:0)
[22:44:39.449] Build status: STARTED
[22:44:39.449] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:12:0) after 9m48s
[22:54:27.469] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:12:0)
[22:54:27.518] Build status: STARTED
[22:54:27.518] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:13:0) after 1m43s
[22:56:10.544] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:13:0)
[22:56:10.565] Build status: STARTED
[22:56:10.565] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:14:0) after 9m11s
[23:05:21.590] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:14:0)
[23:05:21.630] Build status: STARTED
[23:05:21.630] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:15:0) after 4m3s
[23:09:24.650] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:15:0)
[23:09:24.714] Build status: STARTED
[23:09:24.714] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:16:0) after 1m5s
[23:10:29.732] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:16:0)
[23:10:29.802] Build status: STARTED
[23:10:29.802] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:17:0) after 4m23s
[23:14:52.823] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:17:0)
[23:14:52.874] Build status: STARTED
[23:14:52.874] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:18:0) after 6m59s
[23:21:51.895] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:18:0)
[23:21:51.955] Build status: STARTED
[23:21:51.955] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:19:0) after 9m52s
[23:31:43.977] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:19:0)
[23:31:44.013] Build status: STARTED
[23:31:44.013] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:20:0) after 2m55s
[23:34:39.032] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:20:0)
[23:34:39.102] Build status: STARTED
[23:34:39.102] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:21:0) after 9m31s
[23:44:10.119] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:21:0)
[23:44:10.157] Build status: STARTED
[23:44:10.157] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:22:0) after 8m41s
[23:52:51.175] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:22:0)
[23:52:51.196] Build status: STARTED
[23:52:51.196] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:23:0) after 3m46s
[23:56:37.216] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:23:0)
[23:56:37.245] Build status: STARTED
[23:56:37.245] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:24:0) after 1m1s
[23:57:39.192] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:24:0)
[23:57:39.233] Build status: STARTED
[23:57:39.233] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:25:0) after 3m42s
[00:01:21.257] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:25:0)
[00:01:21.279] Build status: STARTED
[00:01:21.279] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:26:0) after 5m7s
[00:06:28.334] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:26:0)
[00:06:28.356] Build status: STARTED
[00:06:28.356] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:27:0) after 4m8s
[00:10:36.387] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:27:0)
[00:10:36.423] Build status: STARTED
[00:10:36.423] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:28:0) after 4m49s
[00:15:25.443] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:28:0)
[00:15:25.485] Build status: STARTED
[00:15:25.485] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:29:0) after 1m53s
[00:17:18.504] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:29:0)
[00:17:18.522] Build status: STARTED
[00:17:18.522] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:30:0) after 3m35s
[00:20:53.543] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:30:0)
[00:20:53.585] Build status: STARTED
[00:20:53.585] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8941079082728897536:31:0) after 7m7s
[00:25:56.079] Received PubSub notification, asking Buildbucket for the build status
[00:25:56.101] Build:
{
"id": "8775649020773944145",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 1518,
"createdBy": "project:chromium",
"createTime": "2023-07-13T22:05:41.300518500Z",
"startTime": "2023-07-13T22:42:11.439545Z",
"endTime": "2023-07-14T00:25:52.263578752Z",
"updateTime": "2023-07-14T00:25:52.263578752Z",
"status": "FAILURE",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "120a605a38ab3085de9bc66c79e29f592f50c332",
"ref": "refs/heads/main"
}
}
}
[00:25:56.101] Invocation finished in 2h20m16.048862986s with status FAILED