[18:02:28.056] New invocation is queued and will start shortly
[18:02:29.112] Starting the invocation (attempt 1)
[18:02:29.140] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/555f16df0961dc6a17ecddef6b8cdc4be8f13074"
[18:02:29.140] Popped gitiles commit info from properties and tags
[18:02:29.140] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[18:02:29.151] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[18:02:29.151] Buildbucket request:
{
"requestId": "8857110995699445536",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "555f16df0961dc6a17ecddef6b8cdc4be8f13074",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8857110995699445536"
},
{
"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:02:29.997] Scheduled build:
{
"id": "8691680933816350161",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 21363,
"createdBy": "project:chromium",
"createTime": "2026-01-25T18:02:29.229347684Z",
"updateTime": "2026-01-25T18:02:29.229347684Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "555f16df0961dc6a17ecddef6b8cdc4be8f13074",
"ref": "refs/heads/main"
}
},
"canary": true
}
[18:02:29.997] Task URL: https://cr-buildbucket-dev.appspot.com/build/8691680933816350161
[18:02:29.997] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:2:0) after 7m12s
[18:02:30.675] Received PubSub notification, asking Buildbucket for the build status
[18:02:30.704] Build status: SCHEDULED
[18:03:48.897] Received PubSub notification, asking Buildbucket for the build status
[18:03:48.917] Build status: STARTED
[18:09:42.011] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:2:0)
[18:09:42.033] Build status: STARTED
[18:09:42.033] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:5:0) after 4m40s
[18:14:22.047] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:5:0)
[18:14:22.067] Build status: STARTED
[18:14:22.067] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:6:0) after 7m58s
[18:22:20.085] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:6:0)
[18:22:20.121] Build status: STARTED
[18:22:20.121] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:7:0) after 7m41s
[18:30:01.136] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:7:0)
[18:30:01.156] Build status: STARTED
[18:30:01.156] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:8:0) after 9m0s
[18:39:01.171] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:8:0)
[18:39:01.188] Build status: STARTED
[18:39:01.188] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:9:0) after 4m7s
[18:43:08.201] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:9:0)
[18:43:08.228] Build status: STARTED
[18:43:08.228] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:10:0) after 6m44s
[18:49:52.241] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:10:0)
[18:49:52.259] Build status: STARTED
[18:49:52.259] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:11:0) after 8m6s
[18:57:58.583] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:11:0)
[18:57:58.599] Build status: STARTED
[18:57:58.599] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:12:0) after 2m31s
[19:00:29.616] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:12:0)
[19:00:29.641] Build status: STARTED
[19:00:29.641] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:13:0) after 1m44s
[19:02:13.658] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:13:0)
[19:02:13.678] Build status: STARTED
[19:02:13.678] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:14:0) after 2m48s
[19:05:01.693] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:14:0)
[19:05:01.710] Build status: STARTED
[19:05:01.710] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:15:0) after 8m6s
[19:13:07.726] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:15:0)
[19:13:07.749] Build status: STARTED
[19:13:07.749] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8857110995699445536:16:0) after 1m26s
[19:14:10.033] Received PubSub notification, asking Buildbucket for the build status
[19:14:10.085] Build:
{
"id": "8691680933816350161",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 21363,
"createdBy": "project:chromium",
"createTime": "2026-01-25T18:02:29.229347684Z",
"startTime": "2026-01-25T18:03:48.660504017Z",
"endTime": "2026-01-25T19:13:41.199400134Z",
"updateTime": "2026-01-25T19:13:41.199400134Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "555f16df0961dc6a17ecddef6b8cdc4be8f13074",
"ref": "refs/heads/main"
}
},
"canary": true
}
[19:14:10.085] Invocation finished in 1h11m42.035175323s with status SUCCEEDED