[13:49:36.052] New invocation is queued and will start shortly
[13:49:37.111] Starting the invocation (attempt 1)
[13:49:37.138] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/b1dd1c8a3185d5a6d72faa6cf10d018c7ecfc00b"
[13:49:37.138] Popped gitiles commit info from properties and tags
[13:49:37.138] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[13:49:37.139] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[13:49:37.139] Buildbucket request:
{
"requestId": "8865733616505093696",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "b1dd1c8a3185d5a6d72faa6cf10d018c7ecfc00b",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8865733616505093696"
},
{
"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"
}
}
[13:49:37.978] Scheduled build:
{
"id": "8700303554635917617",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 20246,
"createdBy": "project:chromium",
"createTime": "2025-10-22T13:49:37.213461689Z",
"updateTime": "2025-10-22T13:49:37.213461689Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "b1dd1c8a3185d5a6d72faa6cf10d018c7ecfc00b",
"ref": "refs/heads/main"
}
}
}
[13:49:37.978] Task URL: https://cr-buildbucket-dev.appspot.com/build/8700303554635917617
[13:49:37.978] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:2:0) after 6m24s
[13:49:38.563] Received PubSub notification, asking Buildbucket for the build status
[13:49:38.589] Build status: SCHEDULED
[13:56:02.000] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:2:0)
[13:56:02.036] Build status: SCHEDULED
[13:56:02.036] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:4:0) after 4m38s
[14:00:40.057] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:4:0)
[14:00:40.083] Build status: SCHEDULED
[14:00:40.083] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:5:0) after 3m37s
[14:04:17.121] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:5:0)
[14:04:17.142] Build status: SCHEDULED
[14:04:17.142] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:6:0) after 5m44s
[14:09:55.083] Received PubSub notification, asking Buildbucket for the build status
[14:09:55.111] Build status: STARTED
[14:10:01.159] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:6:0)
[14:10:01.177] Build status: STARTED
[14:10:01.177] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:8:0) after 8m33s
[14:18:34.200] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:8:0)
[14:18:34.218] Build status: STARTED
[14:18:34.218] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:9:0) after 2m12s
[14:20:46.891] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:9:0)
[14:20:46.912] Build status: STARTED
[14:20:46.912] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:10:0) after 2m0s
[14:22:46.928] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:10:0)
[14:22:46.946] Build status: STARTED
[14:22:46.946] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:11:0) after 8m31s
[14:31:17.966] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:11:0)
[14:31:17.989] Build status: STARTED
[14:31:17.989] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:12:0) after 8m36s
[14:39:54.017] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:12:0)
[14:39:54.042] Build status: STARTED
[14:39:54.042] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:13:0) after 1m3s
[14:40:57.060] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:13:0)
[14:40:57.082] Build status: STARTED
[14:40:57.082] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:14:0) after 5m57s
[14:46:54.107] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:14:0)
[14:46:54.142] Build status: STARTED
[14:46:54.142] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:15:0) after 6m33s
[14:53:27.164] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:15:0)
[14:53:27.192] Build status: STARTED
[14:53:27.192] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:16:0) after 4m12s
[14:57:39.210] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:16:0)
[14:57:39.229] Build status: STARTED
[14:57:39.230] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:17:0) after 1m8s
[14:58:47.259] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:17:0)
[14:58:47.279] Build status: STARTED
[14:58:47.279] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:18:0) after 1m6s
[14:59:53.299] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:18:0)
[14:59:53.315] Build status: STARTED
[14:59:53.315] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:19:0) after 2m3s
[15:01:56.334] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:19:0)
[15:01:56.357] Build status: STARTED
[15:01:56.357] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:20:0) after 3m34s
[15:05:30.374] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:20:0)
[15:05:30.404] Build status: STARTED
[15:05:30.405] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:21:0) after 3m50s
[15:09:20.421] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:21:0)
[15:09:20.449] Build status: STARTED
[15:09:20.449] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:22:0) after 6m50s
[15:16:10.471] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:22:0)
[15:16:10.491] Build status: STARTED
[15:16:10.491] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:23:0) after 4m53s
[15:21:03.508] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:23:0)
[15:21:03.534] Build status: STARTED
[15:21:03.534] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:24:0) after 5m46s
[15:26:49.551] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:24:0)
[15:26:49.569] Build status: STARTED
[15:26:49.569] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:25:0) after 4m37s
[15:31:26.588] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:25:0)
[15:31:26.621] Build status: STARTED
[15:31:26.621] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:26:0) after 4m0s
[15:35:26.639] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:26:0)
[15:35:26.660] Build status: STARTED
[15:35:26.660] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:27:0) after 6m45s
[15:42:11.678] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:27:0)
[15:42:11.707] Build status: STARTED
[15:42:11.707] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:28:0) after 3m18s
[15:45:29.724] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:28:0)
[15:45:29.755] Build status: STARTED
[15:45:29.755] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:29:0) after 9m11s
[15:54:40.781] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:29:0)
[15:54:40.797] Build status: STARTED
[15:54:40.797] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:30:0) after 9m27s
[16:04:07.818] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:30:0)
[16:04:07.848] Build status: STARTED
[16:04:07.849] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8865733616505093696:31:0) after 6m11s
[16:04:09.855] Received PubSub notification, asking Buildbucket for the build status
[16:04:09.876] Build:
{
"id": "8700303554635917617",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 20246,
"createdBy": "project:chromium",
"createTime": "2025-10-22T13:49:37.213461689Z",
"startTime": "2025-10-22T14:09:54.891868581Z",
"endTime": "2025-10-22T16:04:08.849529898Z",
"updateTime": "2025-10-22T16:04:08.849529898Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "b1dd1c8a3185d5a6d72faa6cf10d018c7ecfc00b",
"ref": "refs/heads/main"
}
}
}
[16:04:09.876] Invocation finished in 2h14m33.828706142s with status SUCCEEDED