[08:48:20.045] New invocation is queued and will start shortly
[08:48:21.118] Starting the invocation (attempt 1)
[08:48:21.143] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/26328090b5f9081846d48d05d8e27967573448b8"
[08:48:21.143] Popped gitiles commit info from properties and tags
[08:48:21.143] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[08:48:21.143] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[08:48:21.144] Buildbucket request:
{
"requestId": "8860044961689901392",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "26328090b5f9081846d48d05d8e27967573448b8",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8860044961689901392"
},
{
"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"
}
}
[08:48:22.096] Scheduled build:
{
"id": "8694614899831287889",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 20999,
"createdBy": "project:chromium",
"createTime": "2025-12-24T08:48:21.195925774Z",
"updateTime": "2025-12-24T08:48:21.195925774Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "26328090b5f9081846d48d05d8e27967573448b8",
"ref": "refs/heads/main"
}
},
"canary": true
}
[08:48:22.096] Task URL: https://cr-buildbucket-dev.appspot.com/build/8694614899831287889
[08:48:22.096] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:2:0) after 4m34s
[08:48:22.314] Received PubSub notification, asking Buildbucket for the build status
[08:48:22.337] Build status: SCHEDULED
[08:51:08.254] Received PubSub notification, asking Buildbucket for the build status
[08:51:08.275] Build status: STARTED
[08:52:56.116] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:2:0)
[08:52:56.138] Build status: STARTED
[08:52:56.138] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:5:0) after 5m50s
[08:58:46.152] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:5:0)
[08:58:46.201] Build status: STARTED
[08:58:46.201] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:6:0) after 8m43s
[09:07:29.215] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:6:0)
[09:07:29.233] Build status: STARTED
[09:07:29.234] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:7:0) after 1m14s
[09:08:43.254] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:7:0)
[09:08:43.272] Build status: STARTED
[09:08:43.272] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:8:0) after 4m0s
[09:12:43.293] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:8:0)
[09:12:43.307] Build status: STARTED
[09:12:43.307] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:9:0) after 4m41s
[09:17:24.331] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:9:0)
[09:17:24.394] Build status: STARTED
[09:17:24.394] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:10:0) after 4m14s
[09:21:38.417] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:10:0)
[09:21:38.437] Build status: STARTED
[09:21:38.437] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:11:0) after 9m34s
[09:31:12.454] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:11:0)
[09:31:12.473] Build status: STARTED
[09:31:12.473] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:12:0) after 8m46s
[09:39:58.498] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:12:0)
[09:39:58.531] Build status: STARTED
[09:39:58.531] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:13:0) after 1m21s
[09:41:19.546] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:13:0)
[09:41:19.584] Build status: STARTED
[09:41:19.584] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:14:0) after 6m57s
[09:48:16.602] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:14:0)
[09:48:16.631] Build status: STARTED
[09:48:16.631] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:15:0) after 4m5s
[09:52:21.652] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:15:0)
[09:52:21.675] Build status: STARTED
[09:52:21.675] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:16:0) after 6m27s
[09:58:48.697] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:16:0)
[09:58:48.722] Build status: STARTED
[09:58:48.722] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:17:0) after 8m47s
[10:07:35.738] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:17:0)
[10:07:35.763] Build status: STARTED
[10:07:35.763] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:18:0) after 4m8s
[10:11:43.782] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:18:0)
[10:11:43.811] Build status: STARTED
[10:11:43.811] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:19:0) after 2m25s
[10:14:08.848] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:19:0)
[10:14:08.869] Build status: STARTED
[10:14:08.869] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:20:0) after 6m27s
[10:20:35.887] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:20:0)
[10:20:35.903] Build status: STARTED
[10:20:35.904] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:21:0) after 5m17s
[10:25:52.945] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:21:0)
[10:25:52.969] Build status: STARTED
[10:25:52.969] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:22:0) after 7m50s
[10:33:43.023] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:22:0)
[10:33:43.039] Build status: STARTED
[10:33:43.039] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:23:0) after 7m40s
[10:41:23.070] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:23:0)
[10:41:23.091] Build status: STARTED
[10:41:23.091] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:24:0) after 9m22s
[10:50:45.108] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:24:0)
[10:50:45.125] Build status: STARTED
[10:50:45.125] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:25:0) after 3m33s
[10:54:18.151] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:25:0)
[10:54:18.180] Build status: STARTED
[10:54:18.180] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:26:0) after 5m45s
[11:00:03.196] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:26:0)
[11:00:03.224] Build status: STARTED
[11:00:03.224] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:27:0) after 1m24s
[11:01:27.240] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:27:0)
[11:01:27.258] Build status: STARTED
[11:01:27.258] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:28:0) after 3m12s
[11:04:39.278] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:28:0)
[11:04:39.305] Build status: STARTED
[11:04:39.305] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:29:0) after 5m13s
[11:09:52.328] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:29:0)
[11:09:52.373] Build status: STARTED
[11:09:52.373] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:30:0) after 1m32s
[11:11:24.387] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:30:0)
[11:11:24.403] Build status: STARTED
[11:11:24.403] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860044961689901392:31:0) after 5m25s
[11:11:43.657] Received PubSub notification, asking Buildbucket for the build status
[11:11:43.727] Build:
{
"id": "8694614899831287889",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 20999,
"createdBy": "project:chromium",
"createTime": "2025-12-24T08:48:21.195925774Z",
"startTime": "2025-12-24T08:51:07.522129928Z",
"endTime": "2025-12-24T11:11:26.261091539Z",
"updateTime": "2025-12-24T11:11:26.261091539Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "26328090b5f9081846d48d05d8e27967573448b8",
"ref": "refs/heads/main"
}
},
"canary": true
}
[11:11:43.727] Invocation finished in 2h23m23.688400808s with status SUCCEEDED