[06:20:00.054] New invocation is queued and will start shortly
[06:20:01.113] Starting the invocation (attempt 1)
[06:20:01.139] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/afe88db60018b703d78512673fec4ac36efd464c"
[06:20:01.139] Popped gitiles commit info from properties and tags
[06:20:01.139] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[06:20:01.140] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[06:20:01.140] Buildbucket request:
{
"requestId": "8866939663452447888",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "afe88db60018b703d78512673fec4ac36efd464c",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8866939663452447888"
},
{
"key": "scheduler_job_id",
"value": "chromium/win-local-ssd-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:20:02.455] Scheduled build:
{
"id": "8701509601597552577",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 29145,
"createdBy": "project:chromium",
"createTime": "2025-10-09T06:20:01.202815844Z",
"updateTime": "2025-10-09T06:20:01.202815844Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "afe88db60018b703d78512673fec4ac36efd464c",
"ref": "refs/heads/main"
}
},
"canary": true
}
[06:20:02.455] Task URL: https://cr-buildbucket-dev.appspot.com/build/8701509601597552577
[06:20:02.455] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:2:0) after 1m2s
[06:20:03.344] Received PubSub notification, asking Buildbucket for the build status
[06:20:03.367] Build status: SCHEDULED
[06:21:04.472] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:2:0)
[06:21:04.492] Build status: SCHEDULED
[06:21:04.492] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:4:0) after 1m10s
[06:22:14.510] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:4:0)
[06:22:14.531] Build status: SCHEDULED
[06:22:14.531] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:5:0) after 1m12s
[06:23:26.549] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:5:0)
[06:23:26.572] Build status: SCHEDULED
[06:23:26.572] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:6:0) after 2m40s
[06:26:06.591] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:6:0)
[06:26:06.624] Build status: SCHEDULED
[06:26:06.624] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:7:0) after 6m33s
[06:27:41.417] Received PubSub notification, asking Buildbucket for the build status
[06:27:41.444] Build status: STARTED
[06:32:39.641] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:7:0)
[06:32:39.661] Build status: STARTED
[06:32:39.661] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:9:0) after 1m21s
[06:34:00.677] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:9:0)
[06:34:00.699] Build status: STARTED
[06:34:00.699] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:10:0) after 1m0s
[06:35:00.715] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:10:0)
[06:35:00.742] Build status: STARTED
[06:35:00.742] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:11:0) after 3m52s
[06:38:52.759] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:11:0)
[06:38:52.795] Build status: STARTED
[06:38:52.795] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:12:0) after 4m51s
[06:43:43.812] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:12:0)
[06:43:43.835] Build status: STARTED
[06:43:43.835] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:13:0) after 1m46s
[06:45:29.856] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:13:0)
[06:45:29.877] Build status: STARTED
[06:45:29.877] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:14:0) after 7m24s
[06:52:53.893] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:14:0)
[06:52:53.919] Build status: STARTED
[06:52:53.919] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8866939663452447888:15:0) after 2m54s
[06:53:53.585] Received PubSub notification, asking Buildbucket for the build status
[06:53:53.612] Build:
{
"id": "8701509601597552577",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 29145,
"createdBy": "project:chromium",
"createTime": "2025-10-09T06:20:01.202815844Z",
"startTime": "2025-10-09T06:27:40.755011778Z",
"endTime": "2025-10-09T06:53:52.721832390Z",
"updateTime": "2025-10-09T06:53:52.721832390Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "afe88db60018b703d78512673fec4ac36efd464c",
"ref": "refs/heads/main"
}
},
"canary": true
}
[06:53:53.612] Invocation finished in 33m53.563237893s with status SUCCEEDED