[08:51:05.048] New invocation is queued and will start shortly
[08:51:06.110] Starting the invocation (attempt 1)
[08:51:06.134] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/5c450eb6f0384a705156236947e962550ced7f67"
[08:51:06.134] Popped gitiles commit info from properties and tags
[08:51:06.134] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[08:51:06.137] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[08:51:06.137] Buildbucket request:
{
"requestId": "8900088647820733680",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5c450eb6f0384a705156236947e962550ced7f67",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8900088647820733680"
},
{
"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"
}
}
[08:51:07.160] Scheduled build:
{
"id": "8734658585913051313",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 15260,
"createdBy": "project:chromium",
"createTime": "2024-10-08T08:51:06.245010773Z",
"updateTime": "2024-10-08T08:51:06.245010773Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5c450eb6f0384a705156236947e962550ced7f67",
"ref": "refs/heads/main"
}
},
"canary": true
}
[08:51:07.160] Task URL: https://cr-buildbucket-dev.appspot.com/build/8734658585913051313
[08:51:07.160] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:2:0) after 2m57s
[08:51:07.590] Received PubSub notification, asking Buildbucket for the build status
[08:51:07.626] Build status: SCHEDULED
[08:54:04.175] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:2:0)
[08:54:04.200] Build status: SCHEDULED
[08:54:04.200] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:4:0) after 6m33s
[09:00:37.224] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:4:0)
[09:00:37.256] Build status: SCHEDULED
[09:00:37.256] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:5:0) after 9m53s
[09:10:30.273] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:5:0)
[09:10:30.309] Build status: SCHEDULED
[09:10:30.309] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:6:0) after 3m37s
[09:14:07.337] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:6:0)
[09:14:07.394] Build status: SCHEDULED
[09:14:07.394] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:7:0) after 8m33s
[09:22:40.411] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:7:0)
[09:22:40.443] Build status: SCHEDULED
[09:22:40.443] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:8:0) after 3m40s
[09:26:20.483] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:8:0)
[09:26:20.526] Build status: SCHEDULED
[09:26:20.527] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:9:0) after 7m53s
[09:34:13.545] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:9:0)
[09:34:13.573] Build status: SCHEDULED
[09:34:13.573] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:10:0) after 4m14s
[09:38:27.598] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:10:0)
[09:38:27.636] Build status: SCHEDULED
[09:38:27.636] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:11:0) after 6m54s
[09:39:59.362] Received PubSub notification, asking Buildbucket for the build status
[09:39:59.388] Build status: STARTED
[09:45:21.652] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:11:0)
[09:45:21.680] Build status: STARTED
[09:45:21.680] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:13:0) after 8m24s
[09:53:45.700] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:13:0)
[09:53:45.735] Build status: STARTED
[09:53:45.735] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:14:0) after 3m32s
[09:57:17.754] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:14:0)
[09:57:17.789] Build status: STARTED
[09:57:17.789] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:15:0) after 5m22s
[10:02:39.809] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:15:0)
[10:02:39.870] Build status: STARTED
[10:02:39.870] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:16:0) after 2m22s
[10:05:01.888] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:16:0)
[10:05:01.920] Build status: STARTED
[10:05:01.920] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:17:0) after 9m58s
[10:14:59.937] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:17:0)
[10:14:59.965] Build status: STARTED
[10:14:59.966] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:18:0) after 3m59s
[10:18:58.986] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:18:0)
[10:18:59.026] Build status: STARTED
[10:18:59.026] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:19:0) after 6m51s
[10:25:50.045] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:19:0)
[10:25:50.069] Build status: STARTED
[10:25:50.069] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:20:0) after 1m52s
[10:27:42.088] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:20:0)
[10:27:42.143] Build status: STARTED
[10:27:42.143] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:21:0) after 7m35s
[10:35:17.177] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:21:0)
[10:35:17.279] Build status: STARTED
[10:35:17.279] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:22:0) after 9m40s
[10:44:57.306] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:22:0)
[10:44:57.335] Build status: STARTED
[10:44:57.335] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:23:0) after 7m57s
[10:52:54.368] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:23:0)
[10:52:54.425] Build status: STARTED
[10:52:54.425] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:24:0) after 3m8s
[10:56:02.449] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:24:0)
[10:56:02.527] Build status: STARTED
[10:56:02.527] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:25:0) after 3m46s
[10:59:48.545] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:25:0)
[10:59:48.599] Build status: STARTED
[10:59:48.599] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:26:0) after 2m56s
[11:02:44.618] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:26:0)
[11:02:44.674] Build status: STARTED
[11:02:44.674] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:27:0) after 8m47s
[11:11:31.698] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:27:0)
[11:11:31.734] Build status: STARTED
[11:11:31.734] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:28:0) after 8m58s
[11:20:29.751] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:28:0)
[11:20:29.792] Build status: STARTED
[11:20:29.792] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:29:0) after 5m14s
[11:25:43.810] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:29:0)
[11:25:43.839] Build status: STARTED
[11:25:43.840] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:30:0) after 5m5s
[11:30:48.858] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:30:0)
[11:30:48.926] Build status: STARTED
[11:30:48.926] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:31:0) after 6m20s
[11:37:08.947] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:31:0)
[11:37:08.982] Build status: STARTED
[11:37:08.982] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:32:0) after 8m56s
[11:46:05.006] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:32:0)
[11:46:05.060] Build status: STARTED
[11:46:05.060] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:33:0) after 9m23s
[11:55:28.085] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:33:0)
[11:55:28.135] Build status: STARTED
[11:55:28.135] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:34:0) after 8m33s
[12:04:01.159] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:34:0)
[12:04:01.183] Build status: STARTED
[12:04:01.183] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:35:0) after 3m40s
[12:07:41.203] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:35:0)
[12:07:41.223] Build status: STARTED
[12:07:41.223] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8900088647820733680:36:0) after 3m36s
[12:07:43.614] Received PubSub notification, asking Buildbucket for the build status
[12:07:43.646] Build:
{
"id": "8734658585913051313",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 15260,
"createdBy": "project:chromium",
"createTime": "2024-10-08T08:51:06.245010773Z",
"startTime": "2024-10-08T09:39:59.068647823Z",
"endTime": "2024-10-08T12:07:42.567720950Z",
"updateTime": "2024-10-08T12:07:42.567720950Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "5c450eb6f0384a705156236947e962550ced7f67",
"ref": "refs/heads/main"
}
},
"canary": true
}
[12:07:43.646] Invocation finished in 3h16m38.604288347s with status SUCCEEDED