[18:16:56.046] New invocation is queued and will start shortly
[18:16:57.116] Starting the invocation (attempt 1)
[18:16:57.144] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/bbe6f4e104e3b7c7d0b391277cdef92e26188fc0"
[18:16:57.144] Popped gitiles commit info from properties and tags
[18:16:57.144] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[18:16:57.144] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[18:16:57.144] Buildbucket request:
{
"requestId": "8913008413815399072",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "bbe6f4e104e3b7c7d0b391277cdef92e26188fc0",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8913008413815399072"
},
{
"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"
}
}
[18:16:58.390] Scheduled build:
{
"id": "8747578351913132145",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 7767,
"createdBy": "project:chromium",
"createTime": "2024-05-18T18:16:57.237955201Z",
"updateTime": "2024-05-18T18:16:57.237955201Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "bbe6f4e104e3b7c7d0b391277cdef92e26188fc0",
"ref": "refs/heads/main"
}
},
"canary": true
}
[18:16:58.390] Task URL: https://cr-buildbucket-dev.appspot.com/build/8747578351913132145
[18:16:58.390] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:2:0) after 8m13s
[18:16:58.624] Received PubSub notification, asking Buildbucket for the build status
[18:16:58.661] Build status: SCHEDULED
[18:18:05.548] Received PubSub notification, asking Buildbucket for the build status
[18:18:05.593] Build status: STARTED
[18:25:11.462] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:2:0)
[18:25:11.507] Build status: STARTED
[18:25:11.507] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:5:0) after 2m23s
[18:27:34.532] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:5:0)
[18:27:34.616] Build status: STARTED
[18:27:34.616] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:6:0) after 4m26s
[18:32:00.631] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:6:0)
[18:32:00.797] Build status: STARTED
[18:32:00.797] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:7:0) after 1m48s
[18:33:48.818] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:7:0)
[18:33:48.874] Build status: STARTED
[18:33:48.874] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:8:0) after 4m14s
[18:38:02.897] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:8:0)
[18:38:02.934] Build status: STARTED
[18:38:02.934] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:9:0) after 2m10s
[18:40:12.949] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:9:0)
[18:40:12.996] Build status: STARTED
[18:40:12.996] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:10:0) after 9m52s
[18:50:05.010] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:10:0)
[18:50:05.073] Build status: STARTED
[18:50:05.073] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:11:0) after 2m24s
[18:52:29.094] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:11:0)
[18:52:29.165] Build status: STARTED
[18:52:29.165] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:12:0) after 3m12s
[18:55:41.185] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:12:0)
[18:55:41.217] Build status: STARTED
[18:55:41.217] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:13:0) after 7m36s
[19:03:17.235] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:13:0)
[19:03:17.256] Build status: STARTED
[19:03:17.256] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:14:0) after 5m0s
[19:08:17.288] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:14:0)
[19:08:17.438] Build status: STARTED
[19:08:17.438] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:15:0) after 3m42s
[19:11:59.453] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:15:0)
[19:11:59.528] Build status: STARTED
[19:11:59.528] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913008413815399072:16:0) after 7m3s
[19:15:05.130] Received PubSub notification, asking Buildbucket for the build status
[19:15:05.168] Build:
{
"id": "8747578351913132145",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 7767,
"createdBy": "project:chromium",
"createTime": "2024-05-18T18:16:57.237955201Z",
"startTime": "2024-05-18T18:18:03.844119282Z",
"endTime": "2024-05-18T19:15:03.752380424Z",
"updateTime": "2024-05-18T19:15:03.752380424Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "bbe6f4e104e3b7c7d0b391277cdef92e26188fc0",
"ref": "refs/heads/main"
}
},
"canary": true
}
[19:15:05.168] Invocation finished in 58m9.128649454s with status SUCCEEDED