Skip to content

test(ci): gate the packaged-Host source-launcher smoke on the platfor… #533

test(ci): gate the packaged-Host source-launcher smoke on the platfor…

test(ci): gate the packaged-Host source-launcher smoke on the platfor… #533

Triggered via push September 2, 2026 09:25
Status Failure
Total duration 21m 27s
Artifacts

ci.yml

on: push
Matrix: test
iOS (Kit tests)
4m 1s
iOS (Kit tests)
Signed Windows Release
Signed Windows Release
Notarized macOS Release
Notarized macOS Release
Unsigned Windows Build (testing)
Unsigned Windows Build (testing)
Unsigned Linux Build (testing)
Unsigned Linux Build (testing)
Windows ARM64 Release Candidate Gate
Windows ARM64 Release Candidate Gate
Publish Coordinated Release
0s
Publish Coordinated Release
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 5 warnings
Test (Linux)
Process completed with exit code 1.
src/host-node/HostNodeProductionServe.subprocess.test.ts > production Host CLI subprocess > owns a cold profile, serves the production capability floor, rejects a duplicate lease, and cleans up: src/host-node/HostNodeProductionServe.subprocess.test.ts#L306
AssertionError: (node:10851) ExperimentalWarning: SQLite is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created) taskwraith-host: connect ECONNREFUSED /tmp/twh2-1001-719c9659bb110650/taskwraith-host-v2.sock : expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/host-node/HostNodeProductionServe.subprocess.test.ts:306:83
Test (macOS Intel)
Process completed with exit code 1.
src/host-runtime/HostDiagnosticServe.subprocess.test.ts: src/host-runtime/HostDiagnosticServe.subprocess.test.ts#L85
Error: Hook timed out in 10000ms. If this is a long-running hook, pass a timeout value as the last argument or configure it globally with "hookTimeout". ❯ src/host-runtime/HostDiagnosticServe.subprocess.test.ts:85:1
src/host-runtime/HostEnvelopeVault.test.ts > HostEnvelopeVault > distinguishes a rotated master-key epoch from an ordinary wrong-key authentication failure: src/host-runtime/HostEnvelopeVault.test.ts#L175
AssertionError: expected error to be instance of HostEnvelopeVaultKeyMismatchError - Expected: [Function HostEnvelopeVaultKeyMismatchError] + Received: HostEnvelopeVaultIntegrityError { "message": "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\taskwraith-host-envelope-vault-dcJzS4\\host-envelope-vault\\57950ea16713f579f5911fcf0edebbf15a45a2e725a9ccfcfcd07995fbb94e1f.vault.json has no stable file identity.", "name": "HostEnvelopeVaultIntegrityError", } ❯ src/host-runtime/HostEnvelopeVault.test.ts:175:45
src/host-runtime/HostEnvelopeVault.test.ts > HostEnvelopeVault > detects an in-process rollback of a previously observed generation: src/host-runtime/HostEnvelopeVault.ts#L1060
HostEnvelopeVaultIntegrityError: C:\Users\RUNNER~1\AppData\Local\Temp\taskwraith-host-envelope-vault-xrpp2Q\host-envelope-vault\e28cd65ab25ce03d6051e0f4a1ec51b664586a2e415b67363035d058e7245d16.vault.json has no stable file identity. ❯ fileIdentity src/host-runtime/HostEnvelopeVault.ts:1060:11 ❯ readOptionalPrivateRegularFile src/host-runtime/HostEnvelopeVault.ts:836:22 ❯ HostEnvelopeVault.readEnvelopePath src/host-runtime/HostEnvelopeVault.ts:473:20 ❯ HostEnvelopeVault.readEnvelope src/host-runtime/HostEnvelopeVault.ts:469:17 ❯ HostEnvelopeVault.write src/host-runtime/HostEnvelopeVault.ts:273:27 ❯ src/host-runtime/HostEnvelopeVault.test.ts:163:11
src/host-runtime/HostEnsembleRoundSmoke.subprocess.test.ts > real production Host ensemble smoke > serves a large quarantined ensemble roster and toggles a seat over the real socket: src/host-client/HostProjectionClient.ts#L411
Error: TaskWraith Host discovery paths do not match the configured profile. ❯ HostProjectionClient.connectOnce src/host-client/HostProjectionClient.ts:411:15 ❯ HostProjectionClient.connect src/host-client/HostProjectionClient.ts:376:14 ❯ src/host-runtime/HostEnsembleRoundSmoke.subprocess.test.ts:310:23
src/host-runtime/HostDiagnosticServe.subprocess.test.ts > standalone diagnostic Host subprocess > serves an authenticated degraded projection, rejects a duplicate profile, and cleans up: src/host-client/HostProjectionClient.ts#L411
Error: TaskWraith Host discovery paths do not match the configured profile. ❯ HostProjectionClient.connectOnce src/host-client/HostProjectionClient.ts:411:15 ❯ HostProjectionClient.connect src/host-client/HostProjectionClient.ts:376:14 ❯ src/host-runtime/HostDiagnosticServe.subprocess.test.ts:130:23
src/host-node/HostNodeProductionServe.subprocess.test.ts > production Host CLI subprocess > owns a cold profile, serves the production capability floor, rejects a duplicate lease, and cleans up: src/host-client/HostProjectionClient.ts#L411
Error: TaskWraith Host discovery paths do not match the configured profile. ❯ HostProjectionClient.connectOnce src/host-client/HostProjectionClient.ts:411:15 ❯ HostProjectionClient.connect src/host-client/HostProjectionClient.ts:376:14 ❯ src/host-node/HostNodeProductionServe.subprocess.test.ts:179:23
src/host-node/HostNodeProductionFactory.test.ts > disposes lease-late Muse resources when terminal handoff construction is invalid: src/host-node/HostNodeProductionFactory.test.ts#L647
AssertionError: expected [Function] to throw error including 'handoff' but got 'C:\Users\RUNNER~1\AppData\Local\Temp\…' Expected: "handoff" Received: "C:\Users\RUNNER~1\AppData\Local\Temp\host-node-factory-invalid-launcher-aX0ldf\cold-profile\taskwraith-host-authority-v1.json does not expose a stable file identity for compare-before-release." ❯ src/host-node/HostNodeProductionFactory.test.ts:647:30
src/host-node/HostNodeProductionFactory.test.ts > wires a real optional provider terminal launcher into production auth flows: src/host-node/HostNodeProductionFactory.test.ts#L555
AssertionError: expected { providerId: 'claude', …(3) } to match object { status: 'auth_required' } (3 matching properties omitted from actual) - Expected + Received { - "status": "auth_required", + "status": "degraded", } ❯ src/host-node/HostNodeProductionFactory.test.ts:555:44
src/host-node/HostNodeProductionFactory.test.ts > serves an authenticated cold-profile setup/history workflow and cleans owned resources: src/host-client/HostProjectionClient.ts#L411
Error: TaskWraith Host discovery paths do not match the configured profile. ❯ HostProjectionClient.connectOnce src/host-client/HostProjectionClient.ts:411:15 ❯ HostProjectionClient.connect src/host-client/HostProjectionClient.ts:376:14 ❯ src/host-node/HostNodeProductionFactory.test.ts:414:3
src/host-node/HostNodeProductionFactory.test.ts > composes all static live providers plus guarded AntiGravity on a cold profile: src/host-client/HostProjectionClient.ts#L411
Error: TaskWraith Host discovery paths do not match the configured profile. ❯ HostProjectionClient.connectOnce src/host-client/HostProjectionClient.ts:411:15 ❯ HostProjectionClient.connect src/host-client/HostProjectionClient.ts:376:14 ❯ src/host-node/HostNodeProductionFactory.test.ts:103:3
Unhandled error: src/main/IdentityHandoffService.ts#L716
Error: EPERM: operation not permitted, fsync ❯ IdentityHandoffService.writeState src/main/IdentityHandoffService.ts:716:7 ❯ IdentityHandoffService.fail src/main/IdentityHandoffService.ts:645:12 ❯ src/main/IdentityHandoffService.ts:299:14 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -4048, code: 'EPERM', syscall: 'fsync' } This error originated in "src/main/IdentityHandoffService.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 "coalesces duplicate download requests into one network operation". 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.
iOS (Kit tests)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (Linux)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (macOS Intel)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (Windows)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (macOS Apple Silicon)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/