[20:16:24.075] New invocation is queued and will start shortly
[20:16:25.146] Starting the invocation (attempt 1)
[20:16:25.176] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/1f6ce295789c739790f30ca72837637ccb55828c"
[20:16:25.176] Popped gitiles commit info from properties and tags
[20:16:25.176] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[20:16:25.178] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[20:16:25.178] Buildbucket request:
{
"requestId": "8927677606155165424",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1f6ce295789c739790f30ca72837637ccb55828c",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8927677606155165424"
},
{
"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"
}
}
[20:16:26.642] Scheduled build:
{
"id": "8762247544239864881",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 4319,
"createdBy": "project:chromium",
"createTime": "2023-12-08T20:16:25.272643010Z",
"updateTime": "2023-12-08T20:16:25.272643010Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1f6ce295789c739790f30ca72837637ccb55828c",
"ref": "refs/heads/main"
}
},
"canary": true
}
[20:16:26.642] Task URL: https://cr-buildbucket-dev.appspot.com/build/8762247544239864881
[20:16:26.642] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:2:0) after 2m37s
[20:16:27.139] Received PubSub notification, asking Buildbucket for the build status
[20:16:27.164] Build status: SCHEDULED
[20:19:03.732] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:2:0)
[20:19:03.766] Build status: SCHEDULED
[20:19:03.767] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:4:0) after 3m17s
[20:22:20.796] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:4:0)
[20:22:20.885] Build status: SCHEDULED
[20:22:20.885] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:5:0) after 3m49s
[20:26:09.904] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:5:0)
[20:26:09.929] Build status: SCHEDULED
[20:26:09.929] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:6:0) after 5m41s
[20:31:50.961] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:6:0)
[20:31:51.038] Build status: SCHEDULED
[20:31:51.038] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:7:0) after 9m17s
[20:41:08.057] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:7:0)
[20:41:08.106] Build status: SCHEDULED
[20:41:08.106] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:8:0) after 7m55s
[20:48:05.500] Received PubSub notification, asking Buildbucket for the build status
[20:48:05.531] Build status: STARTED
[20:49:03.132] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:8:0)
[20:49:03.196] Build status: STARTED
[20:49:03.196] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:10:0) after 3m26s
[20:52:29.216] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:10:0)
[20:52:29.269] Build status: STARTED
[20:52:29.269] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:11:0) after 9m58s
[21:02:27.293] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:11:0)
[21:02:27.352] Build status: STARTED
[21:02:27.352] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:12:0) after 3m31s
[21:05:58.374] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:12:0)
[21:05:58.415] Build status: STARTED
[21:05:58.415] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:13:0) after 5m56s
[21:11:54.442] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:13:0)
[21:11:54.477] Build status: STARTED
[21:11:54.477] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:14:0) after 7m12s
[21:19:06.505] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:14:0)
[21:19:06.530] Build status: STARTED
[21:19:06.530] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:15:0) after 6m50s
[21:25:56.555] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:15:0)
[21:25:56.619] Build status: STARTED
[21:25:56.619] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:16:0) after 1m8s
[21:27:05.601] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:16:0)
[21:27:05.667] Build status: STARTED
[21:27:05.667] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:17:0) after 8m27s
[21:35:32.688] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:17:0)
[21:35:32.726] Build status: STARTED
[21:35:32.726] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:18:0) after 3m33s
[21:39:05.750] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:18:0)
[21:39:05.776] Build status: STARTED
[21:39:05.776] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:19:0) after 7m17s
[21:46:22.800] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:19:0)
[21:46:22.844] Build status: STARTED
[21:46:22.844] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:20:0) after 4m49s
[21:51:11.867] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:20:0)
[21:51:11.901] Build status: STARTED
[21:51:11.901] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:21:0) after 3m37s
[21:54:48.926] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:21:0)
[21:54:48.968] Build status: STARTED
[21:54:48.968] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8927677606155165424:22:0) after 8m13s
[21:57:24.851] Received PubSub notification, asking Buildbucket for the build status
[21:57:24.882] Build:
{
"id": "8762247544239864881",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 4319,
"createdBy": "project:chromium",
"createTime": "2023-12-08T20:16:25.272643010Z",
"startTime": "2023-12-08T20:48:03.397149562Z",
"endTime": "2023-12-08T21:57:24.488296543Z",
"updateTime": "2023-12-08T21:57:24.488296543Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1f6ce295789c739790f30ca72837637ccb55828c",
"ref": "refs/heads/main"
}
},
"canary": true
}
[21:57:24.882] Invocation finished in 1h41m0.820478759s with status SUCCEEDED