[11:29:04.050] New invocation is queued and will start shortly
[11:29:05.107] Starting the invocation (attempt 1)
[11:29:05.131] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/f8b78d37419eec40f5f1eb4f4a72a3a792288b60"
[11:29:05.131] Popped gitiles commit info from properties and tags
[11:29:05.131] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[11:29:05.131] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[11:29:05.131] Buildbucket request:
{
"requestId": "8863930518770795264",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "f8b78d37419eec40f5f1eb4f4a72a3a792288b60",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8863930518770795264"
},
{
"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"
}
}
[11:29:06.091] Scheduled build:
{
"id": "8698500456853329969",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 30392,
"createdBy": "project:chromium",
"createTime": "2025-11-11T11:29:05.258874461Z",
"updateTime": "2025-11-11T11:29:05.258874461Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "f8b78d37419eec40f5f1eb4f4a72a3a792288b60",
"ref": "refs/heads/main"
}
},
"canary": true
}
[11:29:06.091] Task URL: https://cr-buildbucket-dev.appspot.com/build/8698500456853329969
[11:29:06.091] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:2:0) after 5m7s
[11:29:06.633] Received PubSub notification, asking Buildbucket for the build status
[11:29:07.714] Build status: SCHEDULED
[11:34:13.104] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:2:0)
[11:34:13.132] Build status: SCHEDULED
[11:34:13.132] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:4:0) after 6m51s
[11:41:04.147] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:4:0)
[11:41:04.164] Build status: SCHEDULED
[11:41:04.164] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:5:0) after 6m18s
[11:47:22.195] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:5:0)
[11:47:22.221] Build status: SCHEDULED
[11:47:22.222] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:6:0) after 5m56s
[11:51:03.448] Received PubSub notification, asking Buildbucket for the build status
[11:51:03.471] Build status: STARTED
[11:53:18.241] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:6:0)
[11:53:18.264] Build status: STARTED
[11:53:18.264] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:8:0) after 6m27s
[11:59:45.278] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:8:0)
[11:59:45.308] Build status: STARTED
[11:59:45.308] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:9:0) after 1m23s
[12:01:08.326] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:9:0)
[12:01:08.351] Build status: STARTED
[12:01:08.351] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:10:0) after 1m7s
[12:02:15.370] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:10:0)
[12:02:15.395] Build status: STARTED
[12:02:15.395] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:11:0) after 1m15s
[12:03:30.419] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:11:0)
[12:03:30.440] Build status: STARTED
[12:03:30.440] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:12:0) after 5m0s
[12:08:30.462] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:12:0)
[12:08:30.484] Build status: STARTED
[12:08:30.484] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:13:0) after 1m16s
[12:09:46.498] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:13:0)
[12:09:46.517] Build status: STARTED
[12:09:46.517] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:14:0) after 5m26s
[12:15:12.530] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:14:0)
[12:15:12.549] Build status: STARTED
[12:15:12.549] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:15:0) after 3m32s
[12:18:44.569] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:15:0)
[12:18:44.599] Build status: STARTED
[12:18:44.599] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:16:0) after 8m8s
[12:26:52.617] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:16:0)
[12:26:52.842] Build status: STARTED
[12:26:52.842] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:17:0) after 8m46s
[12:35:38.860] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:17:0)
[12:35:38.899] Build status: STARTED
[12:35:38.899] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:18:0) after 4m36s
[12:40:14.918] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:18:0)
[12:40:14.947] Build status: STARTED
[12:40:14.947] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:19:0) after 1m15s
[12:41:29.965] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:19:0)
[12:41:29.993] Build status: STARTED
[12:41:29.993] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:20:0) after 2m54s
[12:44:24.007] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:20:0)
[12:44:24.024] Build status: STARTED
[12:44:24.024] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:21:0) after 1m54s
[12:46:18.045] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:21:0)
[12:46:19.421] Build status: STARTED
[12:46:19.421] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:22:0) after 4m27s
[12:50:46.437] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:22:0)
[12:50:46.457] Build status: STARTED
[12:50:46.457] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:23:0) after 1m27s
[12:52:13.478] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:23:0)
[12:52:13.545] Build status: STARTED
[12:52:13.546] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:24:0) after 2m2s
[12:54:15.567] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:24:0)
[12:54:15.597] Build status: STARTED
[12:54:15.597] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:25:0) after 7m23s
[13:01:38.629] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:25:0)
[13:01:38.648] Build status: STARTED
[13:01:38.648] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:26:0) after 5m7s
[13:06:45.670] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:26:0)
[13:06:45.690] Build status: STARTED
[13:06:45.690] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:27:0) after 2m19s
[13:09:04.709] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:27:0)
[13:09:04.744] Build status: STARTED
[13:09:04.744] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:28:0) after 4m18s
[13:13:22.774] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:28:0)
[13:13:22.802] Build status: STARTED
[13:13:22.802] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8863930518770795264:29:0) after 1m56s
[13:13:27.212] Received PubSub notification, asking Buildbucket for the build status
[13:13:27.269] Build:
{
"id": "8698500456853329969",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 30392,
"createdBy": "project:chromium",
"createTime": "2025-11-11T11:29:05.258874461Z",
"startTime": "2025-11-11T11:50:53.101067240Z",
"endTime": "2025-11-11T13:13:26.148948257Z",
"updateTime": "2025-11-11T13:13:26.148948257Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "f8b78d37419eec40f5f1eb4f4a72a3a792288b60",
"ref": "refs/heads/main"
}
},
"canary": true
}
[13:13:27.269] Invocation finished in 1h44m23.223590724s with status SUCCEEDED