[07:43:27.052] New invocation is queued and will start shortly
[07:43:28.120] Starting the invocation (attempt 1)
[07:43:28.146] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/1901ccd1ae2f33923825a1c7233347f9c3fc50e4"
[07:43:28.146] Popped gitiles commit info from properties and tags
[07:43:28.146] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[07:43:28.146] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[07:43:28.146] Buildbucket request:
{
"requestId": "8871645455491098528",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1901ccd1ae2f33923825a1c7233347f9c3fc50e4",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8871645455491098528"
},
{
"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"
}
}
[07:43:29.027] Scheduled build:
{
"id": "8706215393611333201",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 19385,
"createdBy": "project:chromium",
"createTime": "2025-08-18T07:43:28.220128701Z",
"updateTime": "2025-08-18T07:43:28.220128701Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1901ccd1ae2f33923825a1c7233347f9c3fc50e4",
"ref": "refs/heads/main"
}
},
"canary": true
}
[07:43:29.027] Task URL: https://cr-buildbucket-dev.appspot.com/build/8706215393611333201
[07:43:29.027] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:2:0) after 7m50s
[07:43:29.996] Received PubSub notification, asking Buildbucket for the build status
[07:43:30.033] Build status: SCHEDULED
[07:51:19.045] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:2:0)
[07:51:19.073] Build status: SCHEDULED
[07:51:19.073] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:4:0) after 3m26s
[07:54:45.090] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:4:0)
[07:54:45.111] Build status: SCHEDULED
[07:54:45.111] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:5:0) after 1m48s
[07:56:33.128] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:5:0)
[07:56:33.149] Build status: SCHEDULED
[07:56:33.149] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:6:0) after 7m15s
[08:03:48.179] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:6:0)
[08:03:48.219] Build status: SCHEDULED
[08:03:48.219] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:7:0) after 6m17s
[08:10:05.237] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:7:0)
[08:10:05.258] Build status: SCHEDULED
[08:10:05.258] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:8:0) after 2m34s
[08:12:39.276] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:8:0)
[08:12:39.292] Build status: SCHEDULED
[08:12:39.292] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:9:0) after 3m16s
[08:15:55.312] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:9:0)
[08:15:55.333] Build status: SCHEDULED
[08:15:55.333] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:10:0) after 9m17s
[08:25:12.775] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:10:0)
[08:25:12.800] Build status: SCHEDULED
[08:25:12.800] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:11:0) after 7m32s
[08:27:47.188] Received PubSub notification, asking Buildbucket for the build status
[08:27:47.210] Build status: STARTED
[08:32:44.822] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:11:0)
[08:32:44.846] Build status: STARTED
[08:32:44.846] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:13:0) after 5m38s
[08:38:22.865] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:13:0)
[08:38:22.894] Build status: STARTED
[08:38:22.894] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:14:0) after 2m7s
[08:40:29.914] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:14:0)
[08:40:29.974] Build status: STARTED
[08:40:29.974] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:15:0) after 8m54s
[08:49:23.993] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:15:0)
[08:49:24.020] Build status: STARTED
[08:49:24.020] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:16:0) after 9m52s
[08:59:16.038] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:16:0)
[08:59:16.087] Build status: STARTED
[08:59:16.087] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:17:0) after 6m15s
[09:05:31.105] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:17:0)
[09:05:31.177] Build status: STARTED
[09:05:31.177] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:18:0) after 9m15s
[09:14:46.205] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:18:0)
[09:14:46.224] Build status: STARTED
[09:14:46.224] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:19:0) after 8m48s
[09:23:34.244] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:19:0)
[09:23:34.292] Build status: STARTED
[09:23:34.292] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:20:0) after 7m20s
[09:30:54.309] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:20:0)
[09:30:54.354] Build status: STARTED
[09:30:54.354] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:21:0) after 8m15s
[09:39:09.373] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:21:0)
[09:39:09.392] Build status: STARTED
[09:39:09.392] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:22:0) after 6m40s
[09:45:49.410] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:22:0)
[09:45:49.447] Build status: STARTED
[09:45:49.447] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:23:0) after 2m40s
[09:48:29.471] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:23:0)
[09:48:29.517] Build status: STARTED
[09:48:29.517] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:24:0) after 1m17s
[09:49:46.532] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:24:0)
[09:49:46.559] Build status: STARTED
[09:49:46.559] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:25:0) after 8m29s
[09:58:15.579] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:25:0)
[09:58:15.613] Build status: STARTED
[09:58:15.613] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:26:0) after 1m45s
[10:00:00.631] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:26:0)
[10:00:00.658] Build status: STARTED
[10:00:00.658] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:27:0) after 2m3s
[10:02:03.678] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:27:0)
[10:02:03.880] Build status: STARTED
[10:02:03.880] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:28:0) after 2m0s
[10:04:03.923] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:28:0)
[10:04:04.213] Build status: STARTED
[10:04:04.213] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:29:0) after 9m39s
[10:13:43.231] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:29:0)
[10:13:43.256] Build status: STARTED
[10:13:43.256] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:30:0) after 5m39s
[10:19:22.275] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:30:0)
[10:19:22.301] Build status: STARTED
[10:19:22.301] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871645455491098528:31:0) after 7m53s
[10:22:53.570] Received PubSub notification, asking Buildbucket for the build status
[10:22:53.589] Build:
{
"id": "8706215393611333201",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 19385,
"createdBy": "project:chromium",
"createTime": "2025-08-18T07:43:28.220128701Z",
"startTime": "2025-08-18T08:27:46.974180263Z",
"endTime": "2025-08-18T10:22:53.265170139Z",
"updateTime": "2025-08-18T10:22:53.265170139Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1901ccd1ae2f33923825a1c7233347f9c3fc50e4",
"ref": "refs/heads/main"
}
},
"canary": true
}
[10:22:53.589] Invocation finished in 2h39m26.545651656s with status SUCCEEDED