[02:48:06.039] New invocation is queued and will start shortly
[02:48:07.100] Starting the invocation (attempt 1)
[02:48:07.124] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/26e01d94076a715219b96ff036d517c7d7bba3ad"
[02:48:07.124] Popped gitiles commit info from properties and tags
[02:48:07.124] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[02:48:07.124] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[02:48:07.124] Buildbucket request:
{
"requestId": "8890145818462460944",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "26e01d94076a715219b96ff036d517c7d7bba3ad",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8890145818462460944"
},
{
"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"
}
}
[02:48:07.752] Scheduled build:
{
"id": "8724715756607980897",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 15193,
"createdBy": "project:chromium",
"createTime": "2025-01-26T02:48:07.186736522Z",
"updateTime": "2025-01-26T02:48:07.186736522Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "26e01d94076a715219b96ff036d517c7d7bba3ad",
"ref": "refs/heads/main"
}
},
"canary": true
}
[02:48:07.752] Task URL: https://cr-buildbucket-dev.appspot.com/build/8724715756607980897
[02:48:07.752] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:2:0) after 5m31s
[02:48:08.738] Received PubSub notification, asking Buildbucket for the build status
[02:48:08.763] Build status: SCHEDULED
[02:48:15.608] Received PubSub notification, asking Buildbucket for the build status
[02:48:15.639] Build status: STARTED
[02:53:38.769] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:2:0)
[02:53:38.793] Build status: STARTED
[02:53:38.793] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:5:0) after 5m7s
[02:58:45.810] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:5:0)
[02:58:45.855] Build status: STARTED
[02:58:45.855] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:6:0) after 2m9s
[03:00:54.889] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:6:0)
[03:00:54.934] Build status: STARTED
[03:00:54.934] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:7:0) after 7m45s
[03:08:39.950] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:7:0)
[03:08:39.982] Build status: STARTED
[03:08:39.982] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:8:0) after 9m48s
[03:18:28.005] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:8:0)
[03:18:28.036] Build status: STARTED
[03:18:28.036] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:9:0) after 4m28s
[03:22:56.052] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:9:0)
[03:22:56.078] Build status: STARTED
[03:22:56.078] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:10:0) after 3m3s
[03:25:59.096] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:10:0)
[03:25:59.144] Build status: STARTED
[03:25:59.144] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:11:0) after 2m11s
[03:28:10.159] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:11:0)
[03:28:10.193] Build status: STARTED
[03:28:10.193] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:12:0) after 1m46s
[03:29:56.208] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:12:0)
[03:29:56.233] Build status: STARTED
[03:29:56.233] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:13:0) after 2m19s
[03:32:15.249] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:13:0)
[03:32:15.275] Build status: STARTED
[03:32:15.275] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:14:0) after 3m48s
[03:36:03.292] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:14:0)
[03:36:03.315] Build status: STARTED
[03:36:03.315] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:15:0) after 9m54s
[03:45:57.332] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:15:0)
[03:45:57.352] Build status: STARTED
[03:45:57.352] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8890145818462460944:16:0) after 3m22s
[03:49:06.964] Received PubSub notification, asking Buildbucket for the build status
[03:49:06.996] Build:
{
"id": "8724715756607980897",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 15193,
"createdBy": "project:chromium",
"createTime": "2025-01-26T02:48:07.186736522Z",
"startTime": "2025-01-26T02:48:15.337129761Z",
"endTime": "2025-01-26T03:49:06.378511595Z",
"updateTime": "2025-01-26T03:49:06.378511595Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "26e01d94076a715219b96ff036d517c7d7bba3ad",
"ref": "refs/heads/main"
}
},
"canary": true
}
[03:49:06.996] Invocation finished in 1h1m0.962213403s with status SUCCEEDED