[06:21:38.046] New invocation is queued and will start shortly
[06:21:39.128] Starting the invocation (attempt 1)
[06:21:39.153] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/1c30000ac3aba62cb9fa0738f37c50d6becd04ae"
[06:21:39.153] Popped gitiles commit info from properties and tags
[06:21:39.154] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[06:21:39.154] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[06:21:39.154] Buildbucket request:
{
"requestId": "8860688370018615120",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1c30000ac3aba62cb9fa0738f37c50d6becd04ae",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8860688370018615120"
},
{
"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"
}
}
[06:21:39.953] Scheduled build:
{
"id": "8695258308137701537",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 20917,
"createdBy": "project:chromium",
"createTime": "2025-12-17T06:21:39.219758359Z",
"updateTime": "2025-12-17T06:21:39.219758359Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1c30000ac3aba62cb9fa0738f37c50d6becd04ae",
"ref": "refs/heads/main"
}
},
"canary": true
}
[06:21:39.953] Task URL: https://cr-buildbucket-dev.appspot.com/build/8695258308137701537
[06:21:39.953] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:2:0) after 4m9s
[06:21:40.994] Received PubSub notification, asking Buildbucket for the build status
[06:21:41.013] Build status: SCHEDULED
[06:25:48.971] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:2:0)
[06:25:49.006] Build status: SCHEDULED
[06:25:49.006] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:4:0) after 1m13s
[06:27:02.023] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:4:0)
[06:27:02.050] Build status: SCHEDULED
[06:27:02.050] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:5:0) after 9m25s
[06:31:29.766] Received PubSub notification, asking Buildbucket for the build status
[06:31:29.787] Build status: STARTED
[06:36:27.065] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:5:0)
[06:36:27.081] Build status: STARTED
[06:36:27.082] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:7:0) after 3m14s
[06:39:41.098] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:7:0)
[06:39:41.115] Build status: STARTED
[06:39:41.115] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:8:0) after 8m33s
[06:48:14.130] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:8:0)
[06:48:14.148] Build status: STARTED
[06:48:14.148] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:9:0) after 9m47s
[06:58:01.168] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:9:0)
[06:58:01.186] Build status: STARTED
[06:58:01.186] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:10:0) after 9m23s
[07:07:24.225] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:10:0)
[07:07:24.243] Build status: STARTED
[07:07:24.243] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:11:0) after 1m21s
[07:08:46.073] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:11:0)
[07:08:46.093] Build status: STARTED
[07:08:46.093] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:12:0) after 2m27s
[07:11:13.116] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:12:0)
[07:11:13.136] Build status: STARTED
[07:11:13.136] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:13:0) after 4m43s
[07:15:56.150] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:13:0)
[07:15:56.180] Build status: STARTED
[07:15:56.180] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:14:0) after 7m8s
[07:23:04.198] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:14:0)
[07:23:04.215] Build status: STARTED
[07:23:04.215] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:15:0) after 1m10s
[07:24:14.229] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:15:0)
[07:24:14.253] Build status: STARTED
[07:24:14.253] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:16:0) after 3m57s
[07:28:11.276] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:16:0)
[07:28:11.300] Build status: STARTED
[07:28:11.300] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:17:0) after 3m42s
[07:31:53.317] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:17:0)
[07:31:53.336] Build status: STARTED
[07:31:53.336] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:18:0) after 1m14s
[07:33:07.352] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:18:0)
[07:33:07.372] Build status: STARTED
[07:33:07.372] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:19:0) after 7m1s
[07:40:08.388] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:19:0)
[07:40:08.409] Build status: STARTED
[07:40:08.409] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:20:0) after 1m16s
[07:41:24.425] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:20:0)
[07:41:24.451] Build status: STARTED
[07:41:24.451] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:21:0) after 3m43s
[07:45:07.467] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:21:0)
[07:45:07.489] Build status: STARTED
[07:45:07.489] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:22:0) after 8m4s
[07:53:11.512] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:22:0)
[07:53:11.545] Build status: STARTED
[07:53:11.545] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:23:0) after 7m34s
[08:00:45.563] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:23:0)
[08:00:45.580] Build status: STARTED
[08:00:45.580] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:24:0) after 5m56s
[08:06:41.598] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:24:0)
[08:06:41.616] Build status: STARTED
[08:06:41.616] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:25:0) after 6m33s
[08:13:14.634] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:25:0)
[08:13:14.661] Build status: STARTED
[08:13:14.661] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:26:0) after 2m53s
[08:16:07.677] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:26:0)
[08:16:07.695] Build status: STARTED
[08:16:07.695] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:27:0) after 5m16s
[08:21:23.752] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:27:0)
[08:21:23.785] Build status: STARTED
[08:21:23.785] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:28:0) after 3m39s
[08:25:02.800] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:28:0)
[08:25:02.818] Build status: STARTED
[08:25:02.818] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:29:0) after 5m51s
[08:30:53.834] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:29:0)
[08:30:53.852] Build status: STARTED
[08:30:53.852] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:30:0) after 7m15s
[08:38:08.868] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:30:0)
[08:38:08.887] Build status: STARTED
[08:38:08.887] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8860688370018615120:31:0) after 6m8s
[08:41:26.883] Received PubSub notification, asking Buildbucket for the build status
[08:41:26.910] Build:
{
"id": "8695258308137701537",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 20917,
"createdBy": "project:chromium",
"createTime": "2025-12-17T06:21:39.219758359Z",
"startTime": "2025-12-17T06:31:29.587707809Z",
"endTime": "2025-12-17T08:41:26.045644395Z",
"updateTime": "2025-12-17T08:41:26.045644395Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1c30000ac3aba62cb9fa0738f37c50d6becd04ae",
"ref": "refs/heads/main"
}
},
"canary": true
}
[08:41:26.910] Invocation finished in 2h19m48.869260896s with status SUCCEEDED