[11:01:12.078] New invocation is queued and will start shortly
[11:01:13.157] Starting the invocation (attempt 1)
[11:01:13.189] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/6acaeff9cf216adcf01b932248b5283be7a69b8f"
[11:01:13.189] Popped gitiles commit info from properties and tags
[11:01:13.189] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[11:01:13.189] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[11:01:13.190] Buildbucket request:
{
"requestId": "8907781203699467344",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "6acaeff9cf216adcf01b932248b5283be7a69b8f",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8907781203699467344"
},
{
"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"
}
}
[11:01:14.185] Scheduled build:
{
"id": "8742351141799058353",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 8557,
"createdBy": "project:chromium",
"createTime": "2024-07-15T11:01:13.269853409Z",
"updateTime": "2024-07-15T11:01:13.269853409Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "6acaeff9cf216adcf01b932248b5283be7a69b8f",
"ref": "refs/heads/main"
}
},
"canary": true
}
[11:01:14.185] Task URL: https://cr-buildbucket-dev.appspot.com/build/8742351141799058353
[11:01:14.185] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:2:0) after 6m25s
[11:01:14.949] Received PubSub notification, asking Buildbucket for the build status
[11:01:14.982] Build status: SCHEDULED
[11:04:47.118] Received PubSub notification, asking Buildbucket for the build status
[11:04:47.168] Build status: STARTED
[11:07:39.199] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:2:0)
[11:07:39.227] Build status: STARTED
[11:07:39.227] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:5:0) after 3m9s
[11:10:48.244] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:5:0)
[11:10:48.311] Build status: STARTED
[11:10:48.311] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:6:0) after 8m25s
[11:19:13.328] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:6:0)
[11:19:13.371] Build status: STARTED
[11:19:13.371] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:7:0) after 5m49s
[11:25:02.391] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:7:0)
[11:25:02.442] Build status: STARTED
[11:25:02.442] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:8:0) after 5m8s
[11:30:10.468] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:8:0)
[11:30:10.503] Build status: STARTED
[11:30:10.503] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:9:0) after 3m17s
[11:33:27.530] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:9:0)
[11:33:27.559] Build status: STARTED
[11:33:27.559] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:10:0) after 9m46s
[11:43:13.575] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:10:0)
[11:43:13.623] Build status: STARTED
[11:43:13.623] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:11:0) after 3m14s
[11:46:27.639] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:11:0)
[11:46:28.652] Build status: STARTED
[11:46:28.653] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:12:0) after 8m41s
[11:55:09.672] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:12:0)
[11:55:09.700] Build status: STARTED
[11:55:09.700] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:13:0) after 2m57s
[11:58:06.724] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:13:0)
[11:58:06.758] Build status: STARTED
[11:58:06.759] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:14:0) after 4m38s
[12:02:44.780] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:14:0)
[12:02:44.846] Build status: STARTED
[12:02:44.846] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:15:0) after 7m56s
[12:10:40.872] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:15:0)
[12:10:40.907] Build status: STARTED
[12:10:40.907] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8907781203699467344:16:0) after 8m39s
[12:16:42.126] Received PubSub notification, asking Buildbucket for the build status
[12:16:42.162] Build:
{
"id": "8742351141799058353",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 8557,
"createdBy": "project:chromium",
"createTime": "2024-07-15T11:01:13.269853409Z",
"startTime": "2024-07-15T11:04:46.899461793Z",
"endTime": "2024-07-15T12:16:41.671464263Z",
"updateTime": "2024-07-15T12:16:41.671464263Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "6acaeff9cf216adcf01b932248b5283be7a69b8f",
"ref": "refs/heads/main"
}
},
"canary": true
}
[12:16:42.162] Invocation finished in 1h15m30.088218899s with status SUCCEEDED