[09:03:10.044] New invocation is queued and will start shortly
[09:03:11.106] Starting the invocation (attempt 1)
[09:03:11.135] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/693889792750514934856e7c6b6b83df7712234c"
[09:03:11.135] Popped gitiles commit info from properties and tags
[09:03:11.135] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[09:03:11.138] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[09:03:11.138] Buildbucket request:
{
"requestId": "8868650740264758640",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "linux-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "693889792750514934856e7c6b6b83df7712234c",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8868650740264758640"
},
{
"key": "scheduler_job_id",
"value": "chromium/linux-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"
}
}
[09:03:12.038] Scheduled build:
{
"id": "8703220678411892641",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "linux-local-ssd-rel-dev"
},
"number": 75066,
"createdBy": "project:chromium",
"createTime": "2025-09-20T09:03:11.190709594Z",
"updateTime": "2025-09-20T09:03:11.190709594Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "693889792750514934856e7c6b6b83df7712234c",
"ref": "refs/heads/main"
}
}
}
[09:03:12.038] Task URL: https://cr-buildbucket-dev.appspot.com/build/8703220678411892641
[09:03:12.038] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:2:0) after 9m41s
[09:03:12.179] Received PubSub notification, asking Buildbucket for the build status
[09:03:12.211] Build status: SCHEDULED
[09:07:26.403] Received PubSub notification, asking Buildbucket for the build status
[09:07:26.419] Build status: STARTED
[09:12:53.054] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:2:0)
[09:12:53.080] Build status: STARTED
[09:12:53.080] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:5:0) after 3m44s
[09:16:37.094] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:5:0)
[09:16:37.121] Build status: STARTED
[09:16:37.121] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:6:0) after 3m10s
[09:19:47.138] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:6:0)
[09:19:47.155] Build status: STARTED
[09:19:47.155] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:7:0) after 8m2s
[09:27:49.170] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:7:0)
[09:27:49.189] Build status: STARTED
[09:27:49.189] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:8:0) after 9m15s
[09:37:04.207] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:8:0)
[09:37:04.230] Build status: STARTED
[09:37:04.230] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:9:0) after 2m41s
[09:39:45.248] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:9:0)
[09:39:45.266] Build status: STARTED
[09:39:45.266] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:10:0) after 2m27s
[09:42:12.280] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:10:0)
[09:42:12.302] Build status: STARTED
[09:42:12.302] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:11:0) after 1m14s
[09:43:26.398] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:11:0)
[09:43:26.453] Build status: STARTED
[09:43:26.453] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:12:0) after 9m56s
[09:53:22.480] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:12:0)
[09:53:22.502] Build status: STARTED
[09:53:22.502] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:13:0) after 1m6s
[09:54:28.519] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:13:0)
[09:54:28.541] Build status: STARTED
[09:54:28.541] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:14:0) after 8m8s
[10:02:36.558] Handling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:14:0)
[10:02:36.594] Build status: STARTED
[10:02:36.594] Scheduling timer "check-buildbucket-build-status" (chromium/linux-local-ssd-rel-dev:8868650740264758640:15:0) after 8m7s
[10:08:03.102] Received PubSub notification, asking Buildbucket for the build status
[10:08:03.126] Build:
{
"id": "8703220678411892641",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "linux-local-ssd-rel-dev"
},
"number": 75066,
"createdBy": "project:chromium",
"createTime": "2025-09-20T09:03:11.190709594Z",
"startTime": "2025-09-20T09:07:25.670818694Z",
"endTime": "2025-09-20T10:08:02.804171824Z",
"updateTime": "2025-09-20T10:08:02.804171824Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "693889792750514934856e7c6b6b83df7712234c",
"ref": "refs/heads/main"
}
}
}
[10:08:03.126] Invocation finished in 1h4m53.085855934s with status SUCCEEDED