[02:57:12.048] New invocation is queued and will start shortly
[02:57:13.123] Starting the invocation (attempt 1)
[02:57:13.154] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/52cc5d6a59bfd613fa805618458acc77f99474c9"
[02:57:13.154] Popped gitiles commit info from properties and tags
[02:57:13.154] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[02:57:13.155] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[02:57:13.155] Buildbucket request:
{
"requestId": "8888695694470489456",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"properties": {
},
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "52cc5d6a59bfd613fa805618458acc77f99474c9",
"ref": "refs/heads/main"
},
"tags": [
{
"key": "scheduler_invocation_id",
"value": "8888695694470489456"
},
{
"key": "scheduler_job_id",
"value": "chromium/win-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"
}
}
[02:57:13.804] Scheduled build:
{
"id": "8723265632598430545",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 23003,
"createdBy": "project:chromium",
"createTime": "2025-02-11T02:57:13.209457418Z",
"updateTime": "2025-02-11T02:57:13.209457418Z",
"status": "SCHEDULED",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "52cc5d6a59bfd613fa805618458acc77f99474c9",
"ref": "refs/heads/main"
}
},
"canary": true
}
[02:57:13.805] Task URL: https://cr-buildbucket-dev.appspot.com/build/8723265632598430545
[02:57:13.805] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:2:0) after 1m50s
[02:57:14.824] Received PubSub notification, asking Buildbucket for the build status
[02:57:14.845] Build status: SCHEDULED
[02:59:03.823] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:2:0)
[02:59:03.850] Build status: SCHEDULED
[02:59:03.850] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:4:0) after 5m59s
[03:05:03.789] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:4:0)
[03:05:03.802] Build status: SCHEDULED
[03:05:03.802] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:5:0) after 2m13s
[03:07:16.821] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:5:0)
[03:07:16.845] Build status: SCHEDULED
[03:07:16.845] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:6:0) after 9m21s
[03:07:44.161] Received PubSub notification, asking Buildbucket for the build status
[03:07:44.185] Build status: STARTED
[03:16:37.873] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:6:0)
[03:16:37.924] Build status: STARTED
[03:16:37.924] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:8:0) after 9m9s
[03:25:46.945] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:8:0)
[03:25:46.970] Build status: STARTED
[03:25:46.970] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:9:0) after 3m19s
[03:29:05.989] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:9:0)
[03:29:06.015] Build status: STARTED
[03:29:06.015] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:10:0) after 2m15s
[03:31:21.038] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:10:0)
[03:31:21.066] Build status: STARTED
[03:31:21.066] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:11:0) after 2m58s
[03:34:19.089] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:11:0)
[03:34:19.112] Build status: STARTED
[03:34:19.112] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:12:0) after 7m12s
[03:41:31.138] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:12:0)
[03:41:31.170] Build status: STARTED
[03:41:31.170] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:13:0) after 4m22s
[03:45:53.191] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:13:0)
[03:45:53.218] Build status: STARTED
[03:45:53.218] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:14:0) after 9m56s
[03:55:49.240] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:14:0)
[03:55:49.269] Build status: STARTED
[03:55:49.269] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:15:0) after 9m54s
[04:05:43.290] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:15:0)
[04:05:43.316] Build status: STARTED
[04:05:43.316] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:16:0) after 9m44s
[04:15:27.342] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:16:0)
[04:15:27.385] Build status: STARTED
[04:15:27.385] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:17:0) after 6m38s
[04:22:05.411] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:17:0)
[04:22:05.436] Build status: STARTED
[04:22:05.436] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:18:0) after 3m57s
[04:26:02.457] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:18:0)
[04:26:02.486] Build status: STARTED
[04:26:02.486] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:19:0) after 2m0s
[04:28:02.506] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:19:0)
[04:28:02.530] Build status: STARTED
[04:28:02.530] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:20:0) after 9m1s
[04:37:03.564] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:20:0)
[04:37:03.624] Build status: STARTED
[04:37:03.624] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:21:0) after 8m36s
[04:45:39.645] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:21:0)
[04:45:39.670] Build status: STARTED
[04:45:39.670] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:22:0) after 3m8s
[04:48:47.692] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:22:0)
[04:48:47.723] Build status: STARTED
[04:48:47.723] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:23:0) after 2m0s
[04:50:47.753] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:23:0)
[04:50:47.784] Build status: STARTED
[04:50:47.784] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:24:0) after 4m48s
[04:55:35.808] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:24:0)
[04:55:35.832] Build status: STARTED
[04:55:35.832] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:25:0) after 1m48s
[04:57:23.853] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:25:0)
[04:57:23.878] Build status: STARTED
[04:57:23.878] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:26:0) after 4m24s
[05:01:47.907] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:26:0)
[05:01:47.948] Build status: STARTED
[05:01:47.948] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:27:0) after 5m9s
[05:06:56.979] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:27:0)
[05:06:57.010] Build status: STARTED
[05:06:57.010] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:28:0) after 1m45s
[05:08:42.029] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:28:0)
[05:08:42.058] Build status: STARTED
[05:08:42.058] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8888695694470489456:29:0) after 6m30s
[05:13:02.080] Received PubSub notification, asking Buildbucket for the build status
[05:13:02.115] Build:
{
"id": "8723265632598430545",
"builder": {
"project": "chromium",
"bucket": "ci",
"builder": "win-local-ssd-rel-dev"
},
"number": 23003,
"createdBy": "project:chromium",
"createTime": "2025-02-11T02:57:13.209457418Z",
"startTime": "2025-02-11T03:07:43.371143108Z",
"endTime": "2025-02-11T05:13:01.763658288Z",
"updateTime": "2025-02-11T05:13:01.763658288Z",
"status": "SUCCESS",
"input": {
"gitilesCommit": {
"host": "chromium.googlesource.com",
"project": "chromium/src",
"id": "52cc5d6a59bfd613fa805618458acc77f99474c9",
"ref": "refs/heads/main"
}
},
"canary": true
}
[05:13:02.115] Invocation finished in 2h15m50.074949606s with status SUCCEEDED