Skip to content

Attempt entitlements #199

Attempt entitlements

Attempt entitlements #199

Triggered via push September 19, 2024 08:39
Status Failure
Total duration 1h 18m 27s
Artifacts

test.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
Unhandled error: tests/src/setup.ts#L115
internal_error: Source chain error: InvalidCommit error: There already is an undeleted RoleClaim for this role. ❯ catchError ../node_modules/.pnpm/@holochain[email protected]/node_modules/@holochain/client/lib/api/common.js:37:23 ❯ AppWebsocket.callZomeRequester ../node_modules/.pnpm/@holochain[email protected]/node_modules/@holochain/client/lib/api/common.js:13:22 ❯ AppWebsocket.appWs.callZome src/setup.ts:115:22 ❯ RolesClient.createRoleClaim ../node_modules/.pnpm/@darksoil-studio+roles@https+++codeload.github.com+darksoil-studio+roles+tar.gz+b6eb55cff8965_itxw5afjjeswjwvljgl4hnef2a/node_modules/@darksoil-studio/roles/src/roles-client.ts:33:3 ❯ ../node_modules/.pnpm/@darksoil-studio+roles@https+++codeload.github.com+darksoil-studio+roles+tar.gz+b6eb55cff8965_itxw5afjjeswjwvljgl4hnef2a/node_modules/@darksoil-studio/roles/src/roles-store.ts:139:8 This error originated in "src/plenty/orders/producer-invoice.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 "create ProducerInvoice". 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: tests/src/setup.ts#L115
internal_error: Source chain error: InvalidCommit error: There already is an undeleted RoleClaim for this role. ❯ catchError ../node_modules/.pnpm/@holochain[email protected]/node_modules/@holochain/client/lib/api/common.js:37:23 ❯ AppWebsocket.callZomeRequester ../node_modules/.pnpm/@holochain[email protected]/node_modules/@holochain/client/lib/api/common.js:13:22 ❯ AppWebsocket.appWs.callZome src/setup.ts:115:22 ❯ RolesClient.createRoleClaim ../node_modules/.pnpm/@darksoil-studio+roles@https+++codeload.github.com+darksoil-studio+roles+tar.gz+b6eb55cff8965_itxw5afjjeswjwvljgl4hnef2a/node_modules/@darksoil-studio/roles/src/roles-client.ts:33:3 ❯ ../node_modules/.pnpm/@darksoil-studio+roles@https+++codeload.github.com+darksoil-studio+roles+tar.gz+b6eb55cff8965_itxw5afjjeswjwvljgl4hnef2a/node_modules/@darksoil-studio/roles/src/roles-store.ts:139:8 This error originated in "src/plenty/orders/producer-delivery.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 "create and read ProducerDelivery". 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.
src/plenty/orders/order.test.ts > create Order: tests/src/setup.ts#L115
internal_error: Conductor returned an error while using a ConductorApi: DatabaseError(DbConnectionPoolError(Error(Some("unable to open database file: /home/runner/work/_temp/nix-shell.0dSrpg/B7gw-PMlF4ko887d7GD_H/databases/conductor/conductor")))) ❯ catchError ../node_modules/.pnpm/@holochain[email protected]/node_modules/@holochain/client/lib/api/common.js:37:23 ❯ AppWebsocket.callZomeRequester ../node_modules/.pnpm/@holochain[email protected]/node_modules/@holochain/client/lib/api/common.js:13:22 ❯ AppWebsocket.appWs.callZome src/setup.ts:115:22 ❯ src/plenty/orders/order.test.ts:24:5 ❯ Module.runScenario ../node_modules/.pnpm/@holochain[email protected]/node_modules/@holochain/tryorama/lib/local/scenario.js:133:9 ❯ src/plenty/orders/order.test.ts:21:3
testbuild
Process completed with exit code 1.
testbuild
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/