[04:51:48.082] New invocation is queued and will start shortly
[04:51:49.170] Starting the invocation (attempt 1)
[04:51:49.203] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/42a51c96883d1846feb69d32db9e6288b4f14f9a"
[04:51:49.203] Popped gitiles commit info from properties and tags
[04:51:49.203] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[04:51:49.203] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[04:51:49.203] Buildbucket request:
{
"requestId": "8871837448672678896",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "42a51c96883d1846feb69d32db9e6288b4f14f9a",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8871837448672678896"
},
{
"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"
}
}
[04:51:49.808] Scheduled build:
{
"id": "8706407386780120993",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 19355,
"createdBy": "project:chromium",
"createTime": "2025-08-16T04:51:49.266553078Z",
"updateTime": "2025-08-16T04:51:49.266553078Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "42a51c96883d1846feb69d32db9e6288b4f14f9a",
"ref": "refs/heads/main"
}
},
"canary": true
}
[04:51:49.808] Task URL: https://cr-buildbucket-dev.appspot.com/build/8706407386780120993
[04:51:49.808] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:2:0) after 6m54s
[04:51:50.588] Received PubSub notification, asking Buildbucket for the build status
[04:51:50.603] Build status: SCHEDULED
[04:58:43.855] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:2:0)
[04:58:43.876] Build status: SCHEDULED
[04:58:43.876] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:4:0) after 1m5s
[04:59:48.892] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:4:0)
[04:59:48.912] Build status: SCHEDULED
[04:59:48.912] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:5:0) after 9m19s
[05:09:07.929] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:5:0)
[05:09:07.960] Build status: SCHEDULED
[05:09:07.960] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:6:0) after 9m18s
[05:18:25.974] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:6:0)
[05:18:25.997] Build status: SCHEDULED
[05:18:25.997] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:7:0) after 1m28s
[05:19:54.015] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:7:0)
[05:19:54.039] Build status: SCHEDULED
[05:19:54.039] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:8:0) after 6m54s
[05:26:48.976] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:8:0)
[05:26:49.002] Build status: SCHEDULED
[05:26:49.002] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:9:0) after 7m46s
[05:34:35.019] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:9:0)
[05:34:35.043] Build status: SCHEDULED
[05:34:35.043] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:10:0) after 7m23s
[05:39:22.373] Received PubSub notification, asking Buildbucket for the build status
[05:39:22.392] Build status: STARTED
[05:41:58.062] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:10:0)
[05:41:58.085] Build status: STARTED
[05:41:58.086] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:12:0) after 9m31s
[05:51:29.626] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:12:0)
[05:51:29.653] Build status: STARTED
[05:51:29.653] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:13:0) after 8m56s
[06:00:25.683] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:13:0)
[06:00:25.704] Build status: STARTED
[06:00:25.704] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:14:0) after 4m17s
[06:04:42.723] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:14:0)
[06:04:42.768] Build status: STARTED
[06:04:42.768] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:15:0) after 4m38s
[06:09:20.783] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:15:0)
[06:09:20.822] Build status: STARTED
[06:09:20.822] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:16:0) after 2m45s
[06:12:05.851] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:16:0)
[06:12:05.873] Build status: STARTED
[06:12:05.873] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:17:0) after 8m28s
[06:20:33.888] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:17:0)
[06:20:33.906] Build status: STARTED
[06:20:33.906] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:18:0) after 6m37s
[06:27:10.926] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:18:0)
[06:27:10.946] Build status: STARTED
[06:27:10.946] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:19:0) after 6m13s
[06:33:23.959] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:19:0)
[06:33:23.979] Build status: STARTED
[06:33:23.979] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:20:0) after 3m2s
[06:36:25.998] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:20:0)
[06:36:26.031] Build status: STARTED
[06:36:26.031] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:21:0) after 5m11s
[06:41:37.070] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:21:0)
[06:41:37.092] Build status: STARTED
[06:41:37.092] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:22:0) after 4m0s
[06:45:37.109] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:22:0)
[06:45:37.137] Build status: STARTED
[06:45:37.137] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:23:0) after 8m17s
[06:53:54.155] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:23:0)
[06:53:54.178] Build status: STARTED
[06:53:54.178] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:24:0) after 7m1s
[07:00:55.197] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:24:0)
[07:00:55.273] Build status: STARTED
[07:00:55.273] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:25:0) after 9m46s
[07:10:41.289] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:25:0)
[07:10:41.312] Build status: STARTED
[07:10:41.312] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:26:0) after 9m34s
[07:20:15.327] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:26:0)
[07:20:15.355] Build status: STARTED
[07:20:15.355] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:27:0) after 4m49s
[07:25:04.370] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:27:0)
[07:25:04.403] Build status: STARTED
[07:25:04.403] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:28:0) after 3m25s
[07:28:29.419] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:28:0)
[07:28:29.438] Build status: STARTED
[07:28:29.438] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:29:0) after 1m7s
[07:29:36.457] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:29:0)
[07:29:36.477] Build status: STARTED
[07:29:36.477] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:30:0) after 1m59s
[07:31:35.492] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:30:0)
[07:31:35.514] Build status: STARTED
[07:31:35.514] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8871837448672678896:31:0) after 3m52s
[07:34:03.065] Received PubSub notification, asking Buildbucket for the build status
[07:34:03.092] Build:
{
"id": "8706407386780120993",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 19355,
"createdBy": "project:chromium",
"createTime": "2025-08-16T04:51:49.266553078Z",
"startTime": "2025-08-16T05:39:20.351748723Z",
"endTime": "2025-08-16T07:34:02.754204330Z",
"updateTime": "2025-08-16T07:34:02.754204330Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "42a51c96883d1846feb69d32db9e6288b4f14f9a",
"ref": "refs/heads/main"
}
},
"canary": true
}
[07:34:03.092] Invocation finished in 2h42m15.01549061s with status SUCCEEDED