Skip to content

refactor(BA-5650): add owner_id helpers and rename session data types [1/4] #30975

refactor(BA-5650): add owner_id helpers and rename session data types [1/4]

refactor(BA-5650): add owner_id helpers and rename session data types [1/4] #30975

Triggered via pull request April 15, 2026 02:14
Status Failure
Total duration 14m 54s
Artifacts 8

ci.yml

on: pull_request
lint-and-typecheck
6m 26s
lint-and-typecheck
check-alembic-migrations
2m 42s
check-alembic-migrations
Matrix: test-component
Matrix: test-integration
Matrix: test-unit
labeler
6s
labeler
test-component-gate
3s
test-component-gate
test-integration-gate
2s
test-integration-gate
test-unit-gate
3s
test-unit-gate
Matrix: build-scies
build-wheels
0s
build-wheels
build-sbom  /  Discover Dockerfiles
build-sbom / Discover Dockerfiles
build-supergraph
0s
build-supergraph
build-sbom  /  Generate Python SBOM
build-sbom / Generate Python SBOM
build-isla-sorna-image
0s
build-isla-sorna-image
Matrix: build-sbom / Generate Container SBOMs
Waiting for pending jobs
make-final-release
0s
make-final-release
build-conda-pack-for-windows
0s
build-conda-pack-for-windows
Fit to window
Zoom out
Zoom in

Annotations

27 errors and 11 warnings
lint-and-typecheck
Process completed with exit code 1.
lint-and-typecheck
Process completed with exit code 1.
test-unit (0/3)
Process completed with exit code 1.
test-unit (2/3)
Process completed with exit code 1.
test-unit (1/3)
Process completed with exit code 1.
test-unit-gate
Process completed with exit code 1.
test-component (1/2)
badly formed hexadecimal UUID string
test-component (1/2)
badly formed hexadecimal UUID string
test-component (1/2)
badly formed hexadecimal UUID string
test-component (1/2)
badly formed hexadecimal UUID string
test-component (1/2)
badly formed hexadecimal UUID string
test-component (1/2)
badly formed hexadecimal UUID string
test-component (1/2)
badly formed hexadecimal UUID string
test-component (1/2)
badly formed hexadecimal UUID string
test-component (1/2)
badly formed hexadecimal UUID string
test-component (1/2)
badly formed hexadecimal UUID string
test-component (0/2)
badly formed hexadecimal UUID string
test-component (0/2)
badly formed hexadecimal UUID string
test-component (0/2)
badly formed hexadecimal UUID string
test-component (0/2)
badly formed hexadecimal UUID string
test-component (0/2)
badly formed hexadecimal UUID string
test-component (0/2)
badly formed hexadecimal UUID string
test-component (0/2)
badly formed hexadecimal UUID string
test-component (0/2)
badly formed hexadecimal UUID string
test-component (0/2)
badly formed hexadecimal UUID string
test-component (0/2)
badly formed hexadecimal UUID string
test-component-gate
Process completed with exit code 1.
labeler
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/labeler@v5, lablup/auto-label-in-issue@1.7.0, lablup/size-label-action@master. 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/
labeler
Unexpected input(s) 'ignored', valid inputs are ['sizes', 'token']
test-integration (1/2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@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/
test-integration (0/2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@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/
check-alembic-migrations
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, dorny/paths-filter@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/
lint-and-typecheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@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/
test-unit (0/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@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/
test-unit (2/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@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/
test-unit (1/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@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/
test-component (1/2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@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/
test-component (0/2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
pants.lint-and-typecheck.log
989 Bytes
sha256:e5de0b2dc24b51642e0cb7a0bf5db39ca87124db99c7525f31f9924cc1996b0e
pants.test-component.0.log
1.01 KB
sha256:619224d83bf7316c993f368cdca1085be1357a7561cfbc3b9199701d0afa0d34
pants.test-component.1.log
861 Bytes
sha256:6b94958a7f7bd5b4b190b9b24e56fe7ac898fb28271ea2abd7ac5a83fe3b0f09
pants.test-integration.0.log
347 Bytes
sha256:58450c458d1150a4229c4ef799e4a9cfd8b2cba729d05598c4780a6cb5e8267c
pants.test-integration.1.log
347 Bytes
sha256:d2de006b1d9556ce980530694cae0fad95fabf10cee66ea91828f2e38c98dee2
pants.test-unit.0.log
845 Bytes
sha256:fcd33547b9a718fb6e10f9851f9ad831c4418cec2d91f2da699db8c3ff501e7e
pants.test-unit.1.log
851 Bytes
sha256:9de9fb00e72bb284611ff41aa63a07361ea3740791b12c19c9c28be2c5fbe26b
pants.test-unit.2.log
844 Bytes
sha256:bd7e6026cf42c58a97c772d6c58a0f0f65e0e287754bf1c8fab32d1275a2bdbf