chore: add integration docs and test-shims (WIP) #7
Annotations
6 errors and 1 warning
|
test
Process completed with exit code 1.
|
|
tests/integration/cli-edgecases.spec.ts > Integration: CLI edge-cases (NDJSON/stderr/exit) > captures stderr emitted by shim and surfaces on non-zero exit:
src/bot/cli-runner.ts#L4065
CliRunnerError: Failed to spawn CLI: spawn /home/runner/work/SourceBase/SourceBase/test-shims/ob-ndjson-shim.js EACCES (code=EACCES) (errno=-13)
❯ ChildProcess.<anonymous> src/bot/cli-runner.ts:4065:14
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { exitCode: -1, stderr: '\n[spawn error] Failed to spawn CLI: spawn /home/runner/work/SourceBase/SourceBase/test-shims/ob-ndjson-shim.js EACCES (code=EACCES) (errno=-13)' }
|
|
tests/integration/cli-edgecases.spec.ts > Integration: CLI edge-cases (NDJSON/stderr/exit) > consumes NDJSON from a shim and returns success:
src/bot/cli-runner.ts#L4065
CliRunnerError: Failed to spawn CLI: spawn /home/runner/work/SourceBase/SourceBase/test-shims/ob-ndjson-shim.js EACCES (code=EACCES) (errno=-13)
❯ ChildProcess.<anonymous> src/bot/cli-runner.ts:4065:14
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { exitCode: -1, stderr: '\n[spawn error] Failed to spawn CLI: spawn /home/runner/work/SourceBase/SourceBase/test-shims/ob-ndjson-shim.js EACCES (code=EACCES) (errno=-13)' }
|
|
tests/config/bot.test.ts > Bot Config Module > formatConfigError > should show DISCORD_BOT_TOKEN in error when it's missing:
tests/config/bot.test.ts#L147
AssertionError: expected '[stdin]:3\n await import("/h…' to contain 'SUCCESS: Error message contains DISCO…'
- Expected
+ Received
- SUCCESS: Error message contains DISCORD_BOT_TOKEN as expected
+ [stdin]:3
+ await import("/home/runner/work/SourceBase/SourceBase/src/config/bot.ts");
+ ^^^^^
+
+ SyntaxError: await is only valid in async functions and the top level bodies of modules
+ at makeContextifyScript (node:internal/vm:185:14)
+ at node:internal/process/execution:107:22
+ at [stdin]-wrapper:6:24
+ at runScript (node:internal/process/execution:101:62)
+ at asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:11)
+
+ Node.js v20.20.2
+
❯ tests/config/bot.test.ts:147:24
|
|
tests/config/bot.test.ts > Bot Config Module > validation with Discord vars > should fail validation when DISCORD_CHANNEL_ID is missing:
tests/config/bot.test.ts#L92
AssertionError: expected '[stdin]:3\n await import("/h…' to contain 'DISCORD_CHANNEL_ID'
- Expected
+ Received
- DISCORD_CHANNEL_ID
+ [stdin]:3
+ await import("/home/runner/work/SourceBase/SourceBase/src/config/bot.ts");
+ ^^^^^
+
+ SyntaxError: await is only valid in async functions and the top level bodies of modules
+ at makeContextifyScript (node:internal/vm:185:14)
+ at node:internal/process/execution:107:22
+ at [stdin]-wrapper:6:24
+ at runScript (node:internal/process/execution:101:62)
+ at asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:11)
+
+ Node.js v20.20.2
+
❯ tests/config/bot.test.ts:92:24
|
|
tests/config/bot.test.ts > Bot Config Module > validation with Discord vars > should fail validation when DISCORD_BOT_TOKEN is missing:
tests/config/bot.test.ts#L62
AssertionError: expected '[stdin]:3\n await import("/h…' to contain 'DISCORD_BOT_TOKEN'
- Expected
+ Received
- DISCORD_BOT_TOKEN
+ [stdin]:3
+ await import("/home/runner/work/SourceBase/SourceBase/src/config/bot.ts");
+ ^^^^^
+
+ SyntaxError: await is only valid in async functions and the top level bodies of modules
+ at makeContextifyScript (node:internal/vm:185:14)
+ at node:internal/process/execution:107:22
+ at [stdin]-wrapper:6:24
+ at runScript (node:internal/process/execution:101:62)
+ at asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:11)
+
+ Node.js v20.20.2
+
❯ tests/config/bot.test.ts:62:24
|
|
test
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/setup-node@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/
|