refactor(BA-5650): propagate owner_id through scheduler and sokovan [2/4] #30976
jopemachineci.yml
on: pull_request
Matrix: build-scies
build-sbom
/
Generate Python SBOM
build-isla-sorna-image
0s
Matrix: build-sbom / Generate Container SBOMs
Waiting for pending jobs
build-conda-pack-for-windows
0s
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 (1/3)
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-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']
|
|
check-alembic-migrations
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
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/
|
|
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 (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 (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-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
|
991 Bytes |
sha256:ecabba7bd19913c921d087deb6c33cdcd8deae8b11e03596defc489a516b40d6
|
|
|
pants.test-component.0.log
|
1.01 KB |
sha256:e5a461d9e794b55febe8ca4d1254f5565ba12a0d52763504bf4f9c75e76eb49f
|
|
|
pants.test-component.1.log
|
857 Bytes |
sha256:93d4ff9c0c4cae9356ccf641cd7832c0f50add76d173907859aa6dbb36f44651
|
|
|
pants.test-integration.0.log
|
347 Bytes |
sha256:30c847c7cc41bbb6d666b351a94ed0e6c783540d2cde5e050223614c00064794
|
|
|
pants.test-integration.1.log
|
347 Bytes |
sha256:a5da76832d9bb04bf699a8076ac84d9af1be359eb4dd599c5c120d992f771cd4
|
|
|
pants.test-unit.0.log
|
846 Bytes |
sha256:03d96f5ef5f7505199ddd8e8117f4e17e9dc8e504fb0908017e6f0ad2a7185aa
|
|
|
pants.test-unit.1.log
|
849 Bytes |
sha256:9ba4bcbd0b90681306e8370cfd28a8ede8dab7dd55ef81c8b534b1807fb83d29
|
|
|
pants.test-unit.2.log
|
848 Bytes |
sha256:9bfd014e6954baabdd32b739eb76d5d768eeb98858c8efa066ac02e7301f8e0f
|
|