feat(os): add elizaOS live update architecture #29
elizaos-os-release.yml
on: pull_request
Validate OS release surfaces
2m 11s
Annotations
6 errors and 1 warning
|
Validate OS release surfaces
Process completed with exit code 1.
|
|
src/backend/__tests__/executeWritePlan.test.ts > LinuxUsbInstallerBackend.executeWritePlan > Test 5: dd buffered-output heartbeat re-emits last progress while stalled:
packages/os-usb-installer/src/backend/linux-backend.ts#L607
WriteIncompleteError: Write incomplete: expected 1000000000 bytes, wrote 500000000.
❯ LinuxUsbInstallerBackend.executeWritePlan src/backend/linux-backend.ts:607:15
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { expectedBytes: 1000000000, actualBytes: 500000000 }
|
|
src/backend/__tests__/executeWritePlan.test.ts > LinuxUsbInstallerBackend.executeWritePlan > Test 4: final progress(1.0) is emitted for 'write' on success:
packages/os-usb-installer/src/backend/__tests__/executeWritePlan.test.ts#L275
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/backend/__tests__/executeWritePlan.test.ts:275:3
|
|
src/backend/__tests__/executeWritePlan.test.ts > LinuxUsbInstallerBackend.executeWritePlan > Test 3: WriteIncompleteError when bytes written < expected:
packages/os-usb-installer/src/backend/__tests__/executeWritePlan.test.ts#L233
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/backend/__tests__/executeWritePlan.test.ts:233:3
|
|
src/backend/__tests__/executeWritePlan.test.ts > LinuxUsbInstallerBackend.executeWritePlan > Test 2: umount exit code 32 / 'not mounted' is tolerated and dd runs:
packages/os-usb-installer/src/backend/__tests__/executeWritePlan.test.ts#L193
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/backend/__tests__/executeWritePlan.test.ts:193:3
|
|
Unhandled error:
packages/os-usb-installer/src/backend/linux-backend.ts#L607
WriteIncompleteError: Write incomplete: expected 1000000000 bytes, wrote 500000000.
❯ LinuxUsbInstallerBackend.executeWritePlan src/backend/linux-backend.ts:607:15
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { expectedBytes: 1000000000, actualBytes: 500000000 }
This error originated in "src/backend/__tests__/executeWritePlan.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Test 5: dd buffered-output heartbeat re-emits last progress while stalled". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
Validate OS release surfaces
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/upload-artifact@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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
elizaos-os-release-validation
|
1.11 KB |
sha256:a6c83082d8d13bbd13b3fb5d4e17e67b46cf7b4dd429e11fcd5a8c800d97dfa1
|
|