[02:39:28.161] New invocation is queued and will start shortly
[02:39:29.219] Starting the invocation (attempt 1)
[02:39:29.246] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/1587824dc036b6769942524f5fc67fc7cdd29312"
[02:39:29.246] Popped gitiles commit info from properties and tags
[02:39:29.246] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[02:39:29.246] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[02:39:29.246] Buildbucket request:
{
"requestId": "8888787406999925040",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1587824dc036b6769942524f5fc67fc7cdd29312",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8888787406999925040"
},
{
"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:39:29.840] Scheduled build:
{
"id": "8723357345161052209",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 16252,
"createdBy": "project:chromium",
"createTime": "2025-02-10T02:39:29.294773146Z",
"updateTime": "2025-02-10T02:39:29.294773146Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1587824dc036b6769942524f5fc67fc7cdd29312",
"ref": "refs/heads/main"
}
},
"canary": true
}
[02:39:29.840] Task URL: https://cr-buildbucket-dev.appspot.com/build/8723357345161052209
[02:39:29.840] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:2:0) after 3m14s
[02:39:30.229] Received PubSub notification, asking Buildbucket for the build status
[02:39:30.257] Build status: SCHEDULED
[02:39:39.000] Received PubSub notification, asking Buildbucket for the build status
[02:39:39.019] Build status: STARTED
[02:42:43.857] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:2:0)
[02:42:43.888] Build status: STARTED
[02:42:43.888] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:5:0) after 2m32s
[02:45:15.903] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:5:0)
[02:45:15.936] Build status: STARTED
[02:45:15.936] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:6:0) after 1m25s
[02:46:40.951] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:6:0)
[02:46:40.983] Build status: STARTED
[02:46:40.983] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:7:0) after 4m5s
[02:50:46.005] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:7:0)
[02:50:46.026] Build status: STARTED
[02:50:46.026] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:8:0) after 6m58s
[02:57:44.045] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:8:0)
[02:57:44.067] Build status: STARTED
[02:57:44.067] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:9:0) after 3m22s
[03:01:06.083] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:9:0)
[03:01:06.125] Build status: STARTED
[03:01:06.125] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:10:0) after 5m31s
[03:06:37.142] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:10:0)
[03:06:37.165] Build status: STARTED
[03:06:37.165] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:11:0) after 3m18s
[03:09:55.183] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:11:0)
[03:09:55.217] Build status: STARTED
[03:09:55.217] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:12:0) after 4m31s
[03:14:26.236] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:12:0)
[03:14:26.269] Build status: STARTED
[03:14:26.269] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:13:0) after 3m30s
[03:17:56.287] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:13:0)
[03:17:56.307] Build status: STARTED
[03:17:56.307] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:14:0) after 4m30s
[03:22:26.332] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:14:0)
[03:22:26.382] Build status: STARTED
[03:22:26.383] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:15:0) after 4m3s
[03:26:29.400] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:15:0)
[03:26:29.436] Build status: STARTED
[03:26:29.436] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8888787406999925040:16:0) after 3m22s
[03:26:57.943] Received PubSub notification, asking Buildbucket for the build status
[03:26:58.008] Build:
{
"id": "8723357345161052209",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 16252,
"createdBy": "project:chromium",
"createTime": "2025-02-10T02:39:29.294773146Z",
"startTime": "2025-02-10T02:39:38.012866218Z",
"endTime": "2025-02-10T03:26:57.498659211Z",
"updateTime": "2025-02-10T03:26:57.498659211Z",
"status": "FAILURE",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "1587824dc036b6769942524f5fc67fc7cdd29312",
"ref": "refs/heads/main"
}
},
"canary": true
}
[03:26:58.008] Invocation finished in 47m29.851251252s with status FAILED