[04:25:30.056] New invocation is queued and will start shortly
[04:25:31.131] Starting the invocation (attempt 1)
[04:25:31.163] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/1e9f86fe2c897772fcbeefb2795341039c6a7df2"
[04:25:31.163] Popped gitiles commit info from properties and tags
[04:25:31.163] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[04:25:31.163] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[04:25:31.163] Buildbucket request:
{
"requestId": "8901101923501816144",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1e9f86fe2c897772fcbeefb2795341039c6a7df2",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8901101923501816144"
},
{
"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:25:31.879] Scheduled build:
{
"id": "8735671861616848385",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 9607,
"createdBy": "project:chromium",
"createTime": "2024-09-27T04:25:31.231777089Z",
"updateTime": "2024-09-27T04:25:31.231777089Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1e9f86fe2c897772fcbeefb2795341039c6a7df2",
"ref": "refs/heads/main"
}
},
"canary": true
}
[04:25:31.879] Task URL: https://cr-buildbucket-dev.appspot.com/build/8735671861616848385
[04:25:31.879] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:2:0) after 9m41s
[04:25:32.854] Received PubSub notification, asking Buildbucket for the build status
[04:25:32.886] Build status: SCHEDULED
[04:35:12.897] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:2:0)
[04:35:12.941] Build status: SCHEDULED
[04:35:12.941] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:4:0) after 9m20s
[04:38:37.419] Received PubSub notification, asking Buildbucket for the build status
[04:38:37.477] Build status: STARTED
[04:44:32.957] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:4:0)
[04:44:32.988] Build status: STARTED
[04:44:32.988] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:6:0) after 7m21s
[04:51:54.006] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:6:0)
[04:51:54.032] Build status: STARTED
[04:51:54.032] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:7:0) after 9m2s
[05:00:56.049] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:7:0)
[05:00:56.089] Build status: STARTED
[05:00:56.089] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:8:0) after 6m15s
[05:07:11.130] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:8:0)
[05:07:11.154] Build status: STARTED
[05:07:11.154] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:9:0) after 9m45s
[05:16:56.181] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:9:0)
[05:16:57.361] Build status: STARTED
[05:16:57.361] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:10:0) after 4m38s
[05:21:35.379] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:10:0)
[05:21:35.427] Build status: STARTED
[05:21:35.427] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:11:0) after 4m6s
[05:25:41.461] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:11:0)
[05:25:41.487] Build status: STARTED
[05:25:41.487] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:12:0) after 7m12s
[05:32:53.509] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:12:0)
[05:32:53.561] Build status: STARTED
[05:32:53.561] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:13:0) after 2m31s
[05:35:24.582] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:13:0)
[05:35:24.675] Build status: STARTED
[05:35:24.675] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:14:0) after 6m27s
[05:41:51.700] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:14:0)
[05:41:51.752] Build status: STARTED
[05:41:51.752] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:15:0) after 6m13s
[05:48:04.779] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:15:0)
[05:48:04.818] Build status: STARTED
[05:48:04.818] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8901101923501816144:16:0) after 8m48s
[05:48:50.426] Received PubSub notification, asking Buildbucket for the build status
[05:48:50.458] Build:
{
"id": "8735671861616848385",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 9607,
"createdBy": "project:chromium",
"createTime": "2024-09-27T04:25:31.231777089Z",
"startTime": "2024-09-27T04:38:37.200592508Z",
"endTime": "2024-09-27T05:48:49.355061301Z",
"updateTime": "2024-09-27T05:48:49.355061301Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1e9f86fe2c897772fcbeefb2795341039c6a7df2",
"ref": "refs/heads/main"
}
},
"canary": true
}
[05:48:50.458] Invocation finished in 1h23m20.407753096s with status SUCCEEDED