[04:45:54.070] New invocation is queued and will start shortly
[04:45:55.143] Starting the invocation (attempt 1)
[04:45:55.168] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/bbf8fdfcb2b05b3325ec7ef666fda6b9f542ddcc"
[04:45:55.168] Popped gitiles commit info from properties and tags
[04:45:55.168] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[04:45:55.168] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[04:45:55.168] Buildbucket request:
{
"requestId": "8913603021395924560",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "bbf8fdfcb2b05b3325ec7ef666fda6b9f542ddcc",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8913603021395924560"
},
{
"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"
}
}
[04:45:56.007] Scheduled build:
{
"id": "8748172959502091217",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 7497,
"createdBy": "project:chromium",
"createTime": "2024-05-12T04:45:55.251989450Z",
"updateTime": "2024-05-12T04:45:55.251989450Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "bbf8fdfcb2b05b3325ec7ef666fda6b9f542ddcc",
"ref": "refs/heads/main"
}
},
"canary": true
}
[04:45:56.007] Task URL: https://cr-buildbucket-dev.appspot.com/build/8748172959502091217
[04:45:56.007] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:2:0) after 3m21s
[04:45:56.868] Received PubSub notification, asking Buildbucket for the build status
[04:45:56.893] Build status: SCHEDULED
[04:46:04.499] Received PubSub notification, asking Buildbucket for the build status
[04:46:04.523] Build status: STARTED
[04:49:17.026] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:2:0)
[04:49:17.048] Build status: STARTED
[04:49:17.048] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:5:0) after 2m18s
[04:51:35.076] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:5:0)
[04:51:35.156] Build status: STARTED
[04:51:35.156] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:6:0) after 4m48s
[04:56:23.171] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:6:0)
[04:56:23.235] Build status: STARTED
[04:56:23.235] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:7:0) after 1m40s
[04:58:03.252] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:7:0)
[04:58:03.280] Build status: STARTED
[04:58:03.280] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:8:0) after 7m29s
[05:05:32.301] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:8:0)
[05:05:32.326] Build status: STARTED
[05:05:32.326] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:9:0) after 4m56s
[05:10:28.342] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:9:0)
[05:10:28.374] Build status: STARTED
[05:10:28.374] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:10:0) after 2m42s
[05:13:10.390] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:10:0)
[05:13:10.429] Build status: STARTED
[05:13:10.429] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:11:0) after 4m22s
[05:17:32.450] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:11:0)
[05:17:32.472] Build status: STARTED
[05:17:32.473] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:12:0) after 6m48s
[05:24:20.488] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:12:0)
[05:24:20.521] Build status: STARTED
[05:24:20.521] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:13:0) after 2m17s
[05:26:37.536] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:13:0)
[05:26:37.585] Build status: STARTED
[05:26:37.585] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:14:0) after 8m10s
[05:34:47.603] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:14:0)
[05:34:47.639] Build status: STARTED
[05:34:47.639] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:15:0) after 1m13s
[05:36:00.659] Handling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:15:0)
[05:36:00.706] Build status: STARTED
[05:36:00.706] Scheduling timer "check-buildbucket-build-status" (chromium/win-rel-dev:8913603021395924560:16:0) after 5m9s
[05:39:47.516] Received PubSub notification, asking Buildbucket for the build status
[05:39:47.551] Build:
{
"id": "8748172959502091217",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-rel-dev"
},
"number": 7497,
"createdBy": "project:chromium",
"createTime": "2024-05-12T04:45:55.251989450Z",
"startTime": "2024-05-12T04:46:03.152039485Z",
"endTime": "2024-05-12T05:39:46.189381733Z",
"updateTime": "2024-05-12T05:39:46.189381733Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "bbf8fdfcb2b05b3325ec7ef666fda6b9f542ddcc",
"ref": "refs/heads/main"
}
},
"canary": true
}
[05:39:47.551] Invocation finished in 53m53.490366624s with status SUCCEEDED