patch: fix build for typescript native file #1
HungKNguyentest.yml
on: push
Build kernel.c (aarch64)
16s
Build agentd (aarch64-linux-musl)
18s
Matrix: test
Annotations
15 errors and 5 warnings
|
Build kernel.c (aarch64)
The process '/usr/bin/git' failed with exit code 128
|
|
Build kernel.c (aarch64)
Fetched in submodule path 'vendor/libkrunfw', but it did not contain 86dd7fe2293a9bc6428cd642e82a3a2faf6b3a32. Direct fetching of that commit failed.
|
|
Build kernel.c (aarch64)
remote error: upload-pack: not our ref 86dd7fe2293a9bc6428cd642e82a3a2faf6b3a32
|
|
Build agentd (aarch64-linux-musl)
The process '/usr/bin/git' failed with exit code 128
|
|
Build agentd (aarch64-linux-musl)
Fetched in submodule path 'vendor/libkrunfw', but it did not contain 86dd7fe2293a9bc6428cd642e82a3a2faf6b3a32. Direct fetching of that commit failed.
|
|
Build agentd (aarch64-linux-musl)
remote error: upload-pack: not our ref 86dd7fe2293a9bc6428cd642e82a3a2faf6b3a32
|
|
Test (linux-aarch64)
The process '/usr/bin/git' failed with exit code 128
|
|
Test (linux-aarch64)
Fetched in submodule path 'vendor/libkrunfw', but it did not contain 86dd7fe2293a9bc6428cd642e82a3a2faf6b3a32. Direct fetching of that commit failed.
|
|
Test (linux-aarch64)
remote error: upload-pack: not our ref 86dd7fe2293a9bc6428cd642e82a3a2faf6b3a32
|
|
Test (linux-x86_64)
The process '/usr/bin/git' failed with exit code 128
|
|
Test (linux-x86_64)
Fetched in submodule path 'vendor/libkrunfw', but it did not contain 86dd7fe2293a9bc6428cd642e82a3a2faf6b3a32. Direct fetching of that commit failed.
|
|
Test (linux-x86_64)
remote error: upload-pack: not our ref 86dd7fe2293a9bc6428cd642e82a3a2faf6b3a32
|
|
Test (darwin-aarch64)
The process '/opt/homebrew/bin/git' failed with exit code 128
|
|
Test (darwin-aarch64)
Fetched in submodule path 'vendor/libkrunfw', but it did not contain 86dd7fe2293a9bc6428cd642e82a3a2faf6b3a32. Direct fetching of that commit failed.
|
|
Test (darwin-aarch64)
remote error: upload-pack: not our ref 86dd7fe2293a9bc6428cd642e82a3a2faf6b3a32
|
|
Build kernel.c (aarch64)
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 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 agentd (aarch64-linux-musl)
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 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 (linux-aarch64)
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 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 (linux-x86_64)
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 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 (darwin-aarch64)
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 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/
|