Skip to content

feat: Modified the destroy flow to support asking users for identifyi… #85

feat: Modified the destroy flow to support asking users for identifyi…

feat: Modified the destroy flow to support asking users for identifyi… #85

Triggered via push March 11, 2025 00:52
Status Failure
Total duration 54s
Artifacts
build-and-test
43s
build-and-test
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 1 warning
Unhandled error: test/orchestrator/destroy/destroy.test.ts#L39
AssertionError: expected ResourcePlan{ raw: { …(6) }, …(6) } to match object { operation: 'destroy' } (12 matching properties omitted from actual) - Expected + Received - Object { - "operation": "destroy", + ResourcePlan { + "operation": "noop", } ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:1134:13 ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:972:17 ❯ Proxy.methodWrapper node_modules/chai/chai.js:1610:25 ❯ Object.validatePlan test/orchestrator/destroy/destroy.test.ts:39:46 ❯ MockReporter.displayPlan test/orchestrator/mocks/reporter.ts:53:24 ❯ Function.run src/orchestrators/destroy.ts:41:14 ❯ test/orchestrator/destroy/destroy.test.ts:54:5 ❯ node_modules/@vitest/runner/dist/index.js:533:5 ❯ runTest node_modules/@vitest/runner/dist/index.js:1056:11 ❯ runSuite node_modules/@vitest/runner/dist/index.js:1205:15 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. The latest test that might've caused the error is "Can handle a destroy call on a resource that doesn't exist". 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.
Unhandled error: test/orchestrator/destroy/destroy.test.ts#L65
AssertionError: expected null to match object { operation: 'noop' } - Expected: Object { "operation": "noop", } + Received: null ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:1134:13 ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:972:17 ❯ Proxy.methodWrapper node_modules/chai/chai.js:1610:25 ❯ Object.validatePlan test/orchestrator/destroy/destroy.test.ts:65:48 ❯ MockReporter.displayPlan test/orchestrator/mocks/reporter.ts:53:24 ❯ Function.run src/orchestrators/destroy.ts:41:14 ❯ test/orchestrator/destroy/destroy.test.ts:74:5 ❯ node_modules/@vitest/runner/dist/index.js:533:5 ❯ runTest node_modules/@vitest/runner/dist/index.js:1056:11 ❯ runSuite node_modules/@vitest/runner/dist/index.js:1205:15 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. The latest test that might've caused the error is "Can handle destroying only one resource". 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.
test/orchestrator/destroy/destroy.test.ts > Destroy orchestrator tests > Can destroy a resource: test/orchestrator/destroy/destroy.test.ts#L59
AssertionError: expected { propA: 'current', propB: 1, …(2) } to be undefined ❯ test/orchestrator/destroy/destroy.test.ts:59:35
test/orchestrator/destroy/destroy.test.ts > Destroy orchestrator tests > Can handle destroying only one resource: src/orchestrators/destroy.ts#L142
Error: The following resources cannot be imported. No plugins found that support the following types: ["mock.0"] ❯ Function.matchTypeIds src/orchestrators/destroy.ts:142:13 ❯ Function.destroySpecificResources src/orchestrators/destroy.ts:73:31 ❯ Function.run src/orchestrators/destroy.ts:35:35 ❯ test/orchestrator/destroy/destroy.test.ts:101:5
build-and-test
Process completed with exit code 1.
build-and-test
Cache not found for keys: node-cache-Linux-x64-npm-135d3b5b5c00cfece15ee3d4b17aec911ec52131997200c07962df77a56574a9