1. All projects
  2. chromium
  3. win-local-ssd-rel-dev
  4. 8914285422050374256
Status: SUCCEEDED
Triggered by: -
Duration: 2 hours
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": "b475ba099cdf1fe7cafee199115440503f757ae6"
}

Incoming tags

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

Debug log (UTC)

[15:59:26.101] New invocation is queued and will start shortly
[15:59:27.194] Starting the invocation (attempt 1)
[15:59:27.228] Popped buildset tag "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/b475ba099cdf1fe7cafee199115440503f757ae6"
[15:59:27.228] Popped gitiles commit info from properties and tags
[15:59:27.228] Preparing PubSub topic for "https://cr-buildbucket-dev.appspot.com"
[15:59:27.229] PubSub topic is "projects/luci-scheduler-dev/topics/scheduler.buildbucket.cr-buildbucket-dev~appspot.gserviceaccount.com"
[15:59:27.229] Buildbucket request:
{
  "requestId": "8914285422050374256",
  "builder": {
    "project": "chromium",
    "bucket": "ci",
    "builder": "win-local-ssd-rel-dev"
  },
  "properties": {
    },
  "gitilesCommit": {
    "host": "chromium.googlesource.com",
    "project": "chromium/src",
    "id": "b475ba099cdf1fe7cafee199115440503f757ae6",
    "ref": "refs/heads/main"
  },
  "tags": [
    {
      "key": "scheduler_invocation_id",
      "value": "8914285422050374256"
    },
    {
      "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"
  }
}
[15:59:28.221] Scheduled build:
{
  "id": "8748855360093864017",
  "builder": {
    "project": "chromium",
    "bucket": "ci",
    "builder": "win-local-ssd-rel-dev"
  },
  "number": 11254,
  "createdBy": "project:chromium",
  "createTime": "2024-05-04T15:59:27.333434396Z",
  "updateTime": "2024-05-04T15:59:27.333434396Z",
  "status": "SCHEDULED",
  "input": {
    "gitilesCommit": {
      "host": "chromium.googlesource.com",
      "project": "chromium/src",
      "id": "b475ba099cdf1fe7cafee199115440503f757ae6",
      "ref": "refs/heads/main"
    }
  }
}
[15:59:28.221] Task URL: https://cr-buildbucket-dev.appspot.com/build/8748855360093864017
[15:59:28.221] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:2:0) after 7m23s
[15:59:29.054] Received PubSub notification, asking Buildbucket for the build status
[15:59:29.095] Build status: SCHEDULED
[16:06:51.237] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:2:0)
[16:06:51.272] Build status: SCHEDULED
[16:06:51.272] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:4:0) after 8m37s
[16:15:28.301] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:4:0)
[16:15:28.381] Build status: SCHEDULED
[16:15:28.381] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:5:0) after 6m42s
[16:22:10.402] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:5:0)
[16:22:10.486] Build status: SCHEDULED
[16:22:10.486] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:6:0) after 8m45s
[16:30:55.503] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:6:0)
[16:30:55.548] Build status: SCHEDULED
[16:30:55.548] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:7:0) after 4m28s
[16:35:10.678] Received PubSub notification, asking Buildbucket for the build status
[16:35:10.727] Build status: STARTED
[16:35:23.563] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:7:0)
[16:35:23.628] Build status: STARTED
[16:35:23.628] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:9:0) after 1m5s
[16:36:28.643] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:9:0)
[16:36:28.708] Build status: STARTED
[16:36:28.708] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:10:0) after 8m26s
[16:44:54.724] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:10:0)
[16:44:54.754] Build status: STARTED
[16:44:54.754] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:11:0) after 3m30s
[16:48:24.767] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:11:0)
[16:48:24.796] Build status: STARTED
[16:48:24.796] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:12:0) after 8m50s
[16:57:14.819] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:12:0)
[16:57:14.858] Build status: STARTED
[16:57:14.858] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:13:0) after 1m2s
[16:58:16.874] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:13:0)
[16:58:16.916] Build status: STARTED
[16:58:16.916] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:14:0) after 4m13s
[17:02:29.936] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:14:0)
[17:02:29.968] Build status: STARTED
[17:02:29.968] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:15:0) after 1m51s
[17:04:20.984] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:15:0)
[17:04:21.125] Build status: STARTED
[17:04:21.125] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:16:0) after 5m9s
[17:09:30.148] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:16:0)
[17:09:30.211] Build status: STARTED
[17:09:30.212] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:17:0) after 4m49s
[17:14:19.227] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:17:0)
[17:14:19.261] Build status: STARTED
[17:14:19.261] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:18:0) after 2m19s
[17:16:38.281] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:18:0)
[17:16:38.304] Build status: STARTED
[17:16:38.304] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:19:0) after 7m52s
[17:24:30.321] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:19:0)
[17:24:30.394] Build status: STARTED
[17:24:30.394] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:20:0) after 5m52s
[17:30:22.424] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:20:0)
[17:30:22.493] Build status: STARTED
[17:30:22.493] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:21:0) after 5m54s
[17:36:16.537] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:21:0)
[17:36:16.660] Build status: STARTED
[17:36:16.660] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:22:0) after 5m48s
[17:42:04.678] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:22:0)
[17:42:04.720] Build status: STARTED
[17:42:04.720] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:23:0) after 1m26s
[17:43:30.753] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:23:0)
[17:43:30.816] Build status: STARTED
[17:43:30.816] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:24:0) after 9m9s
[17:52:39.838] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:24:0)
[17:52:39.876] Build status: STARTED
[17:52:39.876] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:25:0) after 9m0s
[18:01:39.906] Handling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:25:0)
[18:01:39.946] Build status: STARTED
[18:01:39.946] Scheduling timer "check-buildbucket-build-status" (chromium/win-local-ssd-rel-dev:8914285422050374256:26:0) after 9m27s
[18:06:46.400] Received PubSub notification, asking Buildbucket for the build status
[18:06:46.426] Build:
{
  "id": "8748855360093864017",
  "builder": {
    "project": "chromium",
    "bucket": "ci",
    "builder": "win-local-ssd-rel-dev"
  },
  "number": 11254,
  "createdBy": "project:chromium",
  "createTime": "2024-05-04T15:59:27.333434396Z",
  "startTime": "2024-05-04T16:35:09.173873668Z",
  "endTime": "2024-05-04T18:06:45.938812588Z",
  "updateTime": "2024-05-04T18:06:45.938812588Z",
  "status": "SUCCESS",
  "input": {
    "gitilesCommit": {
      "host": "chromium.googlesource.com",
      "project": "chromium/src",
      "id": "b475ba099cdf1fe7cafee199115440503f757ae6",
      "ref": "refs/heads/main"
    }
  }
}
[18:06:46.426] Invocation finished in 2h7m20.342397767s with status SUCCEEDED