[14:19:27.047] New invocation is queued and will start shortly
[14:19:28.104] Starting the invocation (attempt 1)
[14:19:28.131] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/5c051dc0b73b46cf139b5786bea67c00a7fbe8c4"
[14:19:28.131] Popped gitiles commit info from properties and tags
[14:19:28.131] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[14:19:28.131] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[14:19:28.131] Buildbucket request:
{
"requestId": "8857125026703118176",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5c051dc0b73b46cf139b5786bea67c00a7fbe8c4",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8857125026703118176"
},
{
"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"
}
}
[14:19:28.932] Scheduled build:
{
"id": "8691694964857510801",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 21361,
"createdBy": "project:chromium",
"createTime": "2026-01-25T14:19:28.185555601Z",
"updateTime": "2026-01-25T14:19:28.185555601Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5c051dc0b73b46cf139b5786bea67c00a7fbe8c4",
"ref": "refs/heads/main"
}
},
"canary": true
}
[14:19:28.932] Task URL: https://cr-buildbucket-dev.appspot.com/build/8691694964857510801
[14:19:28.932] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:2:0) after 3m16s
[14:19:29.916] Received PubSub notification, asking Buildbucket for the build status
[14:19:29.936] Build status: SCHEDULED
[14:22:44.946] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:2:0)
[14:22:44.967] Build status: SCHEDULED
[14:22:44.967] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:4:0) after 3m32s
[14:26:16.985] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:4:0)
[14:26:17.001] Build status: SCHEDULED
[14:26:17.002] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:5:0) after 6m25s
[14:27:54.047] Received PubSub notification, asking Buildbucket for the build status
[14:27:54.064] Build status: STARTED
[14:32:42.017] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:5:0)
[14:32:42.035] Build status: STARTED
[14:32:42.035] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:7:0) after 4m35s
[14:37:17.055] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:7:0)
[14:37:17.072] Build status: STARTED
[14:37:17.072] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:8:0) after 6m58s
[14:44:15.088] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:8:0)
[14:44:15.104] Build status: STARTED
[14:44:15.104] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:9:0) after 4m54s
[14:49:09.118] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:9:0)
[14:49:09.135] Build status: STARTED
[14:49:09.135] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:10:0) after 9m10s
[14:58:19.150] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:10:0)
[14:58:19.170] Build status: STARTED
[14:58:19.170] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:11:0) after 3m5s
[15:01:24.184] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:11:0)
[15:01:24.201] Build status: STARTED
[15:01:24.201] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:12:0) after 2m8s
[15:03:32.220] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:12:0)
[15:03:32.238] Build status: STARTED
[15:03:32.238] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:13:0) after 5m15s
[15:08:47.253] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:13:0)
[15:08:47.274] Build status: STARTED
[15:08:47.274] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:14:0) after 5m42s
[15:14:29.287] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:14:0)
[15:14:29.309] Build status: STARTED
[15:14:29.309] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:15:0) after 1m39s
[15:16:08.323] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:15:0)
[15:16:08.358] Build status: STARTED
[15:16:08.358] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:16:0) after 4m31s
[15:20:39.805] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:16:0)
[15:20:39.821] Build status: STARTED
[15:20:39.821] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:17:0) after 4m51s
[15:25:31.295] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:17:0)
[15:25:31.318] Build status: STARTED
[15:25:31.318] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:18:0) after 6m1s
[15:31:32.332] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:18:0)
[15:31:32.352] Build status: STARTED
[15:31:32.352] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:19:0) after 5m32s
[15:37:04.369] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:19:0)
[15:37:04.386] Build status: STARTED
[15:37:04.386] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:20:0) after 4m54s
[15:41:58.414] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:20:0)
[15:41:58.441] Build status: STARTED
[15:41:58.441] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:21:0) after 7m2s
[15:49:00.458] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:21:0)
[15:49:00.477] Build status: STARTED
[15:49:00.477] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:22:0) after 6m37s
[15:55:37.491] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:22:0)
[15:55:37.576] Build status: STARTED
[15:55:37.576] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:23:0) after 8m25s
[16:04:02.588] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:23:0)
[16:04:02.783] Build status: STARTED
[16:04:02.783] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:24:0) after 5m3s
[16:09:05.797] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:24:0)
[16:09:05.815] Build status: STARTED
[16:09:05.815] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:25:0) after 1m29s
[16:10:34.830] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:25:0)
[16:10:34.848] Build status: STARTED
[16:10:34.848] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:26:0) after 5m57s
[16:16:31.863] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:26:0)
[16:16:31.891] Build status: STARTED
[16:16:31.891] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:27:0) after 4m27s
[16:20:58.904] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:27:0)
[16:20:58.921] Build status: STARTED
[16:20:58.921] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:28:0) after 8m9s
[16:29:07.933] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:28:0)
[16:29:07.950] Build status: STARTED
[16:29:07.950] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:29:0) after 2m52s
[16:31:59.967] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:29:0)
[16:31:59.988] Build status: STARTED
[16:31:59.988] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:30:0) after 2m47s
[16:34:47.006] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:30:0)
[16:34:47.030] Build status: STARTED
[16:34:47.030] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857125026703118176:31:0) after 3m28s
[16:36:36.411] Received PubSub notification, asking Buildbucket for the build status
[16:36:36.431] Build:
{
"id": "8691694964857510801",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 21361,
"createdBy": "project:chromium",
"createTime": "2026-01-25T14:19:28.185555601Z",
"startTime": "2026-01-25T14:27:53.885043090Z",
"endTime": "2026-01-25T16:36:35.535435215Z",
"updateTime": "2026-01-25T16:36:35.535435215Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5c051dc0b73b46cf139b5786bea67c00a7fbe8c4",
"ref": "refs/heads/main"
}
},
"canary": true
}
[16:36:36.431] Invocation finished in 2h17m9.388893971s with status SUCCEEDED