Skip to content

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

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] #30956

Triggered via pull request April 15, 2026 01:52
Status Failure
Total duration 14m 43s
Artifacts 8

ci.yml

on: pull_request
lint-and-typecheck
6m 34s
lint-and-typecheck
check-alembic-migrations
2m 53s
check-alembic-migrations
Matrix: test-component
Matrix: test-integration
Matrix: test-unit
labeler
8s
labeler
test-component-gate
2s
test-component-gate
test-integration-gate
2s
test-integration-gate
test-unit-gate
2s
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 (1/3)
Process completed with exit code 1.
test-unit (2/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 (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-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-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
984 Bytes
sha256:f53699ed66f6f33d0097ccbe9f44034d92d3d0191cb3dde47c0a47a32681ae14
pants.test-component.0.log
1020 Bytes
sha256:ecca5fd8e72c329735f9deb8435bca66881d6d596aa279f9e15c6a102d2663cd
pants.test-component.1.log
853 Bytes
sha256:bc7464de07b6e0c2dee9011b4f0b5de8e05a59d27b56758eba28aea6fb57efbf
pants.test-integration.0.log
348 Bytes
sha256:f08059702e935b5ceeb4bce0b6b8336a2da69c247be037ccb18ca47128e3e0b1
pants.test-integration.1.log
348 Bytes
sha256:c947e83e6b487b7742a5536530f2aafa65610f7d5bb17b7a72bbe5044686d939
pants.test-unit.0.log
834 Bytes
sha256:fffd8019f7490c033feee4304e999949a8ac9a8d3ac5b33b35889de79e593197
pants.test-unit.1.log
848 Bytes
sha256:5512328e29bfaae2fd6bdb35059287ac45c014860b71bb5d777d3d187f61e616
pants.test-unit.2.log
851 Bytes
sha256:e4a4cb46b314b0a28b01a1977567ee2428ae194b01f746d612777c0cf7763893