Add wait_for_next_message so CT002 serves fresh powermeter data #631
tomquistci.yml
on: pull_request
lint
13s
Matrix: validate
Matrix: build-addon
Matrix: build
merge-addon
/
merge
merge
/
merge
Annotations
16 errors and 10 warnings
|
build (linux/amd64, base-linux-amd64) / build
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
build (linux/amd64, base-linux-amd64) / build
The operation was canceled.
|
|
build-addon (linux/arm64, addon-linux-arm64) / build
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
build-addon (linux/arm64, addon-linux-arm64) / build
The operation was canceled.
|
|
build (linux/arm64, base-linux-arm64) / build
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
build (linux/arm64, base-linux-arm64) / build
The operation was canceled.
|
|
build (linux/arm/v7, base-linux-arm-v7) / build
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
build (linux/arm/v7, base-linux-arm-v7) / build
The operation was canceled.
|
|
build-addon (linux/amd64, addon-linux-amd64) / build
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
build-addon (linux/amd64, addon-linux-amd64) / build
The operation was canceled.
|
|
CI Pipeline
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
CI Pipeline
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
CI Pipeline
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
CI Pipeline
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
CI Pipeline
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
CI Pipeline
Canceling since a higher priority waiting request for ci-CI Pipeline-refs/pull/322/merge exists
|
|
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, astral-sh/setup-uv@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
validate (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, astral-sh/setup-uv@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
validate (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, astral-sh/setup-uv@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
validate (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, astral-sh/setup-uv@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
validate (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, astral-sh/setup-uv@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (linux/amd64, base-linux-amd64) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-addon (linux/arm64, addon-linux-arm64) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (linux/arm64, base-linux-arm64) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (linux/arm/v7, base-linux-arm-v7) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-addon (linux/amd64, addon-linux-amd64) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
coverage-3.10
|
17.2 KB |
sha256:c45eff2c0eac6f082493a0e7f15f94d7febb8e789da820274aa76eef7af3294e
|
|
|
coverage-3.11
|
17.2 KB |
sha256:9cf04bdae9ee32950c1cc26c2510d856318283cbd47f70b63bda716b17c11e90
|
|
|
coverage-3.12
|
17.2 KB |
sha256:806d604fda475257e7c97edab2dc6dd2de42e3560cd85e5c3505c6bd2bbb87e5
|
|
|
coverage-3.13
|
17.2 KB |
sha256:59f76b5a46b2947c572b1e8dfe9efc24357218c958e2cff76f633a2baba81b47
|
|
|
test-results-3.10
|
7.29 KB |
sha256:cb317907c89b089e19deac68771c94cb23d0fd117aedfb6bd7796d3ffc7a0e87
|
|
|
test-results-3.11
|
7.3 KB |
sha256:439baefd5b1204a362041273ec58b13463b63a823603f60e24df3c9984c14237
|
|
|
test-results-3.12
|
7.26 KB |
sha256:e077b3d5aef2bc9cea4cc3ef04a42147eb2c21d106dbe506e24c3e184bdb15b1
|
|
|
test-results-3.13
|
7.23 KB |
sha256:f805000c9e7c4fa4a4c993af9d3561ebdbcbac559e2aa4070739373f856ba314
|
|