[09:41:30.060] New invocation is queued and will start shortly
[09:41:31.128] Starting the invocation (attempt 1)
[09:41:31.152] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/52b014e167af7b617e31308ee49c9f856c34efdd"
[09:41:31.152] Popped gitiles commit info from properties and tags
[09:41:31.152] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[09:41:31.152] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[09:41:31.152] Buildbucket request:
{
"requestId": "8869916686057003776",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "52b014e167af7b617e31308ee49c9f856c34efdd",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8869916686057003776"
},
{
"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"
}
}
[09:41:31.849] Scheduled build:
{
"id": "8704486624202776113",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 19624,
"createdBy": "project:chromium",
"createTime": "2025-09-06T09:41:31.204743906Z",
"updateTime": "2025-09-06T09:41:31.204743906Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "52b014e167af7b617e31308ee49c9f856c34efdd",
"ref": "refs/heads/main"
}
},
"canary": true
}
[09:41:31.849] Task URL: https://cr-buildbucket-dev.appspot.com/build/8704486624202776113
[09:41:31.849] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:2:0) after 1m19s
[09:41:32.840] Received PubSub notification, asking Buildbucket for the build status
[09:41:32.862] Build status: SCHEDULED
[09:42:48.623] Received PubSub notification, asking Buildbucket for the build status
[09:42:48.749] Build status: STARTED
[09:42:50.865] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:2:0)
[09:42:50.891] Build status: STARTED
[09:42:50.891] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:5:0) after 6m20s
[09:49:10.888] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:5:0)
[09:49:10.919] Build status: STARTED
[09:49:10.919] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:6:0) after 4m2s
[09:53:12.930] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:6:0)
[09:53:12.951] Build status: STARTED
[09:53:12.951] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:7:0) after 4m16s
[09:57:28.999] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:7:0)
[09:57:29.061] Build status: STARTED
[09:57:29.061] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:8:0) after 5m47s
[10:03:16.077] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:8:0)
[10:03:16.112] Build status: STARTED
[10:03:16.112] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:9:0) after 8m4s
[10:11:20.141] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:9:0)
[10:11:20.423] Build status: STARTED
[10:11:20.423] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:10:0) after 7m35s
[10:18:55.447] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:10:0)
[10:18:55.474] Build status: STARTED
[10:18:55.475] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:11:0) after 9m7s
[10:28:02.490] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:11:0)
[10:28:02.538] Build status: STARTED
[10:28:02.538] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:12:0) after 2m41s
[10:30:43.553] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:12:0)
[10:30:43.591] Build status: STARTED
[10:30:43.591] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:13:0) after 5m47s
[10:36:30.605] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:13:0)
[10:36:30.652] Build status: STARTED
[10:36:30.652] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:14:0) after 8m5s
[10:44:35.669] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:14:0)
[10:44:35.702] Build status: STARTED
[10:44:35.702] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:15:0) after 4m35s
[10:49:10.718] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:15:0)
[10:49:10.738] Build status: STARTED
[10:49:10.739] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8869916686057003776:16:0) after 8m56s
[10:56:00.055] Received PubSub notification, asking Buildbucket for the build status
[10:56:00.078] Build:
{
"id": "8704486624202776113",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 19624,
"createdBy": "project:chromium",
"createTime": "2025-09-06T09:41:31.204743906Z",
"startTime": "2025-09-06T09:42:47.820939367Z",
"endTime": "2025-09-06T10:55:59.620173236Z",
"updateTime": "2025-09-06T10:55:59.620173236Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "52b014e167af7b617e31308ee49c9f856c34efdd",
"ref": "refs/heads/main"
}
},
"canary": true
}
[10:56:00.078] Invocation finished in 1h14m30.025707199s with status SUCCEEDED