1. All projects
  2. chromium
  3. win-local-ssd-rel-dev
  4. 8906057841797894000
Status: SUCCEEDED
Triggered by: -
Duration: 1 hour
Actions:

Definition (rev d26de8fd7e7c6024960cc7da46d0bd18da72c782) 

buildbucket: <
  server: "cr-buildbucket-dev.appspot.com"
  bucket: "ci"
  builder: "win-local-ssd-rel-dev"
>

Incoming triggers

Incoming properties

{
  "branch": "refs/heads/main",
  "repository": "https://chromium.googlesource.com/chromium/src",
  "revision": "e4851d39be1d478aaad0e9d5c778eed7f1b789f8"
}

Incoming tags

  • buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/e4851d39be1d478aaad0e9d5c778eed7f1b789f8
  • gitiles_ref:refs/heads/main

Debug log (UTC)

[11:33:18.062] New invocation is queued and will start shortly
[11:33:19.126] Starting the invocation (attempt 1)
[11:33:19.157] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/e4851d39be1d478aaad0e9d5c778eed7f1b789f8"
[11:33:19.157] Popped gitiles commit info from properties and tags
[11:33:19.157] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[11:33:19.157] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[11:33:19.157] Buildbucket request:
{
  "requestId": "8906057841797894000",
  "builder": {
    "project": "chromium",
    "bucket": "ci",
    "builder": "win-local-ssd-rel-dev"
  },
  "properties": {
    },
  "gitilesCommit": {
    "host": "chromium.googlesource.com",
    "project": "chromium/src",
    "id": "e4851d39be1d478aaad0e9d5c778eed7f1b789f8",
    "ref": "refs/heads/main"
  },
  "tags": [
    {
      "key": "scheduler_invocation_id",
      "value": "8906057841797894000"
    },
    {
      "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"
  }
}
[11:33:20.015] Scheduled build:
{
  "id": "8740627779913493329",
  "builder": {
    "project": "chromium",
    "bucket": "ci",
    "builder": "win-local-ssd-rel-dev"
  },
  "number": 13648,
  "createdBy": "project:chromium",
  "createTime": "2024-08-03T11:33:19.237737119Z",
  "updateTime": "2024-08-03T11:33:19.237737119Z",
  "status": "SCHEDULED",
  "input": {
    "gitilesCommit": {
      "host": "chromium.googlesource.com",
      "project": "chromium/src",
      "id": "e4851d39be1d478aaad0e9d5c778eed7f1b789f8",
      "ref": "refs/heads/main"
    }
  }
}
[11:33:20.015] Task URL: https://cr-buildbucket-dev.appspot.com/build/8740627779913493329
[11:33:20.015] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:2:0) after 1m54s
[11:33:21.969] Received PubSub notification, asking Buildbucket for the build status
[11:33:22.009] Build status: SCHEDULED
[11:33:28.953] Received PubSub notification, asking Buildbucket for the build status
[11:33:28.995] Build status: STARTED
[11:35:14.030] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:2:0)
[11:35:14.076] Build status: STARTED
[11:35:14.076] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:5:0) after 7m26s
[11:42:40.093] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:5:0)
[11:42:40.126] Build status: STARTED
[11:42:40.126] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:6:0) after 4m59s
[11:47:39.147] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:6:0)
[11:47:39.208] Build status: STARTED
[11:47:39.208] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:7:0) after 2m42s
[11:50:21.223] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:7:0)
[11:50:21.243] Build status: STARTED
[11:50:21.243] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:8:0) after 1m4s
[11:51:25.268] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:8:0)
[11:51:25.317] Build status: STARTED
[11:51:25.317] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:9:0) after 5m23s
[11:56:48.331] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:9:0)
[11:56:48.378] Build status: STARTED
[11:56:48.378] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:10:0) after 7m4s
[12:03:52.397] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:10:0)
[12:03:52.440] Build status: STARTED
[12:03:52.440] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:11:0) after 3m6s
[12:06:58.458] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:11:0)
[12:06:58.488] Build status: STARTED
[12:06:58.488] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:12:0) after 2m6s
[12:09:04.509] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:12:0)
[12:09:04.544] Build status: STARTED
[12:09:04.544] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:13:0) after 2m53s
[12:11:57.560] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:13:0)
[12:11:57.594] Build status: STARTED
[12:11:57.594] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:14:0) after 2m26s
[12:14:23.607] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:14:0)
[12:14:23.640] Build status: STARTED
[12:14:23.640] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:15:0) after 3m29s
[12:17:52.657] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:15:0)
[12:17:52.691] Build status: STARTED
[12:17:52.691] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:16:0) after 2m49s
[12:20:41.706] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:16:0)
[12:20:41.732] Build status: STARTED
[12:20:41.732] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:17:0) after 6m19s
[12:27:00.748] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:17:0)
[12:27:00.789] Build status: STARTED
[12:27:00.790] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:18:0) after 1m35s
[12:28:35.805] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:18:0)
[12:28:35.837] Build status: STARTED
[12:28:35.837] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:19:0) after 5m22s
[12:33:57.865] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:19:0)
[12:33:57.906] Build status: STARTED
[12:33:57.906] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:20:0) after 5m39s
[12:39:36.926] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:20:0)
[12:39:36.974] Build status: STARTED
[12:39:36.974] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:21:0) after 8m37s
[12:48:13.988] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:21:0)
[12:48:14.025] Build status: STARTED
[12:48:14.025] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:22:0) after 1m56s
[12:50:10.050] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:22:0)
[12:50:10.090] Build status: STARTED
[12:50:10.090] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:23:0) after 4m46s
[12:54:56.108] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:23:0)
[12:54:56.149] Build status: STARTED
[12:54:56.149] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:24:0) after 8m24s
[13:03:20.170] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:24:0)
[13:03:20.199] Build status: STARTED
[13:03:20.199] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:25:0) after 5m54s
[13:09:14.214] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:25:0)
[13:09:14.257] Build status: STARTED
[13:09:14.257] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8906057841797894000:26:0) after 9m15s
[13:16:25.187] Received PubSub notification, asking Buildbucket for the build status
[13:16:25.221] Build:
{
  "id": "8740627779913493329",
  "builder": {
    "project": "chromium",
    "bucket": "ci",
    "builder": "win-local-ssd-rel-dev"
  },
  "number": 13648,
  "createdBy": "project:chromium",
  "createTime": "2024-08-03T11:33:19.237737119Z",
  "startTime": "2024-08-03T11:33:26.807564553Z",
  "endTime": "2024-08-03T13:16:24.795652880Z",
  "updateTime": "2024-08-03T13:16:24.795652880Z",
  "status": "SUCCESS",
  "input": {
    "gitilesCommit": {
      "host": "chromium.googlesource.com",
      "project": "chromium/src",
      "id": "e4851d39be1d478aaad0e9d5c778eed7f1b789f8",
      "ref": "refs/heads/main"
    }
  }
}
[13:16:25.221] Invocation finished in 1h43m7.165335819s with status SUCCEEDED