[18:21:54.049] New invocation is queued and will start shortly
[18:21:55.129] Starting the invocation (attempt 1)
[18:21:55.156] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/35fa1bfb35a4a9be34f6c33e973500f820c09242"
[18:21:55.156] Popped gitiles commit info from properties and tags
[18:21:55.156] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[18:21:55.158] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[18:21:55.159] Buildbucket request:
{
"requestId": "8893710947495557856",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "35fa1bfb35a4a9be34f6c33e973500f820c09242",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8893710947495557856"
},
{
"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"
}
}
[18:21:55.825] Scheduled build:
{
"id": "8728280885618735793",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 14569,
"createdBy": "project:chromium",
"createTime": "2024-12-17T18:21:55.213871806Z",
"updateTime": "2024-12-17T18:21:55.213871806Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "35fa1bfb35a4a9be34f6c33e973500f820c09242",
"ref": "refs/heads/main"
}
},
"canary": true
}
[18:21:55.825] Task URL: https://cr-buildbucket-dev.appspot.com/build/8728280885618735793
[18:21:55.825] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:2:0) after 1m15s
[18:22:36.965] Received PubSub notification, asking Buildbucket for the build status
[18:22:36.984] Build status: SCHEDULED
[18:23:10.848] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:2:0)
[18:23:10.881] Build status: SCHEDULED
[18:23:10.881] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:4:0) after 1m50s
[18:24:45.540] Received PubSub notification, asking Buildbucket for the build status
[18:24:45.574] Build status: STARTED
[18:25:00.900] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:4:0)
[18:25:00.929] Build status: STARTED
[18:25:00.929] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:6:0) after 1m10s
[18:26:10.946] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:6:0)
[18:26:11.022] Build status: STARTED
[18:26:11.022] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:7:0) after 5m1s
[18:31:12.042] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:7:0)
[18:31:12.073] Build status: STARTED
[18:31:12.073] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:8:0) after 9m11s
[18:40:23.091] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:8:0)
[18:40:23.123] Build status: STARTED
[18:40:23.123] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:9:0) after 7m52s
[18:48:15.138] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:9:0)
[18:48:15.163] Build status: STARTED
[18:48:15.163] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:10:0) after 3m45s
[18:52:00.180] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:10:0)
[18:52:00.197] Build status: STARTED
[18:52:00.197] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:11:0) after 9m47s
[19:01:47.229] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:11:0)
[19:01:47.399] Build status: STARTED
[19:01:47.399] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:12:0) after 3m17s
[19:05:04.416] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:12:0)
[19:05:04.452] Build status: STARTED
[19:05:04.452] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:13:0) after 4m2s
[19:09:06.471] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:13:0)
[19:09:06.501] Build status: STARTED
[19:09:06.501] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:14:0) after 6m39s
[19:15:45.520] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:14:0)
[19:15:45.544] Build status: STARTED
[19:15:45.544] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:15:0) after 5m11s
[19:20:56.563] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:15:0)
[19:20:56.585] Build status: STARTED
[19:20:56.585] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:16:0) after 5m50s
[19:26:46.604] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:16:0)
[19:26:46.628] Build status: STARTED
[19:26:46.628] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:17:0) after 2m27s
[19:29:13.674] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:17:0)
[19:29:13.693] Build status: STARTED
[19:29:13.693] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:18:0) after 1m49s
[19:31:02.709] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:18:0)
[19:31:02.738] Build status: STARTED
[19:31:02.738] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:19:0) after 3m53s
[19:34:55.757] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:19:0)
[19:34:55.816] Build status: STARTED
[19:34:55.816] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:20:0) after 5m51s
[19:40:46.835] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:20:0)
[19:40:46.888] Build status: STARTED
[19:40:46.888] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:21:0) after 4m45s
[19:45:31.906] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:21:0)
[19:45:31.929] Build status: STARTED
[19:45:31.929] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:22:0) after 1m3s
[19:46:34.945] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:22:0)
[19:46:34.978] Build status: STARTED
[19:46:34.978] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:23:0) after 6m42s
[19:53:17.005] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:23:0)
[19:53:17.046] Build status: STARTED
[19:53:17.046] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:24:0) after 3m4s
[19:56:21.063] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:24:0)
[19:56:21.093] Build status: STARTED
[19:56:21.093] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:25:0) after 8m45s
[20:05:06.109] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:25:0)
[20:05:06.141] Build status: STARTED
[20:05:06.141] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:26:0) after 7m21s
[20:12:27.161] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:26:0)
[20:12:27.191] Build status: STARTED
[20:12:27.191] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:27:0) after 8m30s
[20:20:57.208] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:27:0)
[20:20:57.279] Build status: STARTED
[20:20:57.279] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:28:0) after 6m44s
[20:27:41.296] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:28:0)
[20:27:41.314] Build status: STARTED
[20:27:41.314] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:29:0) after 3m36s
[20:31:17.332] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:29:0)
[20:31:17.386] Build status: STARTED
[20:31:17.386] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:30:0) after 1m6s
[20:32:23.409] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:30:0)
[20:32:23.433] Build status: STARTED
[20:32:23.433] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8893710947495557856:31:0) after 8m17s
[20:38:41.798] Received PubSub notification, asking Buildbucket for the build status
[20:38:41.825] Build:
{
"id": "8728280885618735793",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 14569,
"createdBy": "project:chromium",
"createTime": "2024-12-17T18:21:55.213871806Z",
"startTime": "2024-12-17T18:24:45.312969225Z",
"endTime": "2024-12-17T20:38:40.843689505Z",
"updateTime": "2024-12-17T20:38:40.843689505Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "35fa1bfb35a4a9be34f6c33e973500f820c09242",
"ref": "refs/heads/main"
}
},
"canary": true
}
[20:38:41.825] Invocation finished in 2h16m47.784846715s with status SUCCEEDED