Skip to content

feat: Switched to using identifying parameters #62

feat: Switched to using identifying parameters

feat: Switched to using identifying parameters #62

Triggered via push February 19, 2025 15:12
Status Failure
Total duration 49s
Artifacts
build-and-test
37s
build-and-test
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
Unhandled error: src/plugins/plugin-manager.ts#L183
TypeError: p.kill is not a function ❯ src/plugins/plugin-manager.ts:183:11 ❯ process.kill src/plugins/plugin-manager.ts:182:15 ❯ process.emit node:events:530:35 ❯ Signal.callbackTrampoline node:internal/async_hooks:130:17 This error originated in "test/orchestrator/import/import.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. This error was caught after test environment was torn down. Make sure to cancel any running tasks before test finishes: - cancel timeouts using clearTimeout and clearInterval - wait for promises to resolve using the await keyword
Unhandled error: src/plugins/plugin-manager.ts#L183
TypeError: p.kill is not a function ❯ src/plugins/plugin-manager.ts:183:11 ❯ process.kill src/plugins/plugin-manager.ts:182:15 ❯ process.emit node:events:530:35 ❯ Signal.callbackTrampoline node:internal/async_hooks:130:17 This error originated in "test/orchestrator/apply/apply.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. This error was caught after test environment was torn down. Make sure to cancel any running tasks before test finishes: - cancel timeouts using clearTimeout and clearInterval - wait for promises to resolve using the await keyword
Unhandled error: src/plugins/plugin-manager.ts#L183
TypeError: p.kill is not a function ❯ src/plugins/plugin-manager.ts:183:11 ❯ process.kill src/plugins/plugin-manager.ts:182:15 ❯ process.emit node:events:530:35 ❯ Signal.callbackTrampoline node:internal/async_hooks:130:17 This error originated in "test/orchestrator/plan/plan.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. This error was caught after test environment was torn down. Make sure to cancel any running tasks before test finishes: - cancel timeouts using clearTimeout and clearInterval - wait for promises to resolve using the await keyword
Unhandled error: src/plugins/plugin-manager.ts#L183
TypeError: p.kill is not a function ❯ src/plugins/plugin-manager.ts:183:11 ❯ process.kill src/plugins/plugin-manager.ts:182:15 ❯ process.emit node:events:530:35 This error originated in "test/orchestrator/initialize/initialize.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. This error was caught after test environment was torn down. Make sure to cancel any running tasks before test finishes: - cancel timeouts using clearTimeout and clearInterval - wait for promises to resolve using the await keyword
Unhandled error: src/plugins/plugin-manager.ts#L183
TypeError: p.kill is not a function ❯ src/plugins/plugin-manager.ts:183:11 ❯ process.kill src/plugins/plugin-manager.ts:182:15 ❯ process.emit node:events:530:35 ❯ Signal.callbackTrampoline node:internal/async_hooks:130:17 This error originated in "test/orchestrator/destroy/destroy.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. This error was caught after test environment was torn down. Make sure to cancel any running tasks before test finishes: - cancel timeouts using clearTimeout and clearInterval - wait for promises to resolve using the await keyword
src/entities/resource-config.test.ts > Resource config unit tests > detects if two resource configs represent the same thing on the system (different required parameters): src/entities/resource-config.test.ts#L125
AssertionError: expected true to be false - Expected + Received - false + true ❯ src/entities/resource-config.test.ts:125:52
src/utils/file-modification-calculator.test.ts > File modification calculator tests > Can update a resource in an existing config: src/utils/file-modification-calculator.test.ts#L226
AssertionError: expected '[\n {\n "type": "project",\n "…' to equal '[\n {\n "type": "project",\n "…' - Expected + Received [ { "type": "project", "plugins": { "default": "latest" } }, { "type": "resource1", - "param2": ["a","b","c","d"] + "param2": [ + "a", + "b", + "c", + "d" + ] } ] ❯ src/utils/file-modification-calculator.test.ts:226:31
test/orchestrator/import/import.test.ts > Import orchestrator tests > Can import a resource (no project) and can save to a new file: test/orchestrator/import/import.test.ts#L186
Error: ENOENT: no such file or directory, open '/import.codify.json' ❯ createError node_modules/memfs/src/node/util.ts:146:17 ❯ Volume.walk node_modules/memfs/src/volume.ts:469:46 ❯ Volume.getResolvedLinkOrThrow node_modules/memfs/src/volume.ts:504:17 ❯ Volume.readFileBase node_modules/memfs/src/volume.ts:961:31 ❯ Volume.readFileSync node_modules/memfs/src/volume.ts:983:17 ❯ test/orchestrator/import/import.test.ts:186:28 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ENOENT', path: '/import.codify.json' }
test/orchestrator/import/import.test.ts > Import orchestrator tests > Can import a resource and save it into an existing project (multiple codify files): test/orchestrator/import/import.test.ts#L428
AssertionError: expected [ { type: 'alias', …(2) }, …(1) ] to match object [ { type: 'alias', …(2) }, …(2) ] - Expected + Received Array [ Object { "alias": "gcdsdd", "type": "alias", "value": "git clone", }, Object { - "alias": "gcc", - "type": "alias", - "value": "git commit -v", - }, - Object { "alias": "gc-new", "type": "alias", "value": "gc-new-value", }, ] ❯ test/orchestrator/import/import.test.ts:428:41
build-and-test
Process completed with exit code 1.
build-and-test
Cache not found for keys: node-cache-Linux-x64-npm-b35cb8bea4559ac994a442a3858a2e5ca65f234f0512f68b00ca7ae240774a24