Skip to content
Triggered via push September 26, 2024 12:21
Status Cancelled
Total duration 7m 20s
Artifacts

e2e-node.yml

on: push
Matrix: e2e-node
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 5 warnings
e2e-node (ubuntu-latest, 22.x, ESS PodSpaces, false)
Canceling since a higher priority waiting request for 'End-to-end node tests-refs/heads/exp/node-e2e' exists
e2e-node (ubuntu-latest, 22.x, ESS PodSpaces, false)
The operation was canceled.
e2e-node (ubuntu-latest, 22.x, ESS Dev-2-2, false)
Canceling since a higher priority waiting request for 'End-to-end node tests-refs/heads/exp/node-e2e' exists
e2e-node (ubuntu-latest, 22.x, ESS Dev-2-2, false)
The operation was canceled.
e2e-node (ESS Dev-2-3, true, ubuntu-latest, .nvmrc)
Canceling since a higher priority waiting request for 'End-to-end node tests-refs/heads/exp/node-e2e' exists
e2e-node (ubuntu-latest, 20.x, ESS Dev-2-2, false)
Canceling since a higher priority waiting request for 'End-to-end node tests-refs/heads/exp/node-e2e' exists
Testing against express app with session keep alive off › Should be able to properly login and out with idp logout: e2e/node/server/e2e-app-test.spec.ts#L160
thrown: "Exceeded timeout of 30000 ms for a hook. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at e2e/node/server/e2e-app-test.spec.ts:160:13 at Object.<anonymous> (e2e/node/server/e2e-app-test.spec.ts:156:9)
e2e-node (ubuntu-latest, 20.x, ESS Dev-2-2, false)
The operation was canceled.
Testing against express app with session keep alive off › Should be able to properly login and out with idp logout: e2e/browser/solid-client-authn-browser/test/fixtures.ts#L108
An async callback is still failing after 5 retries. The errors were: Error: Deleting the file at [https://storage.dev-2-3.inrupt.com/04c44f1c-647d-447d-a5a9-2c44a66470ff/f272057d-47ac-4d7c-a436-bc6c47a4e76e] failed: [401] [Unauthorized] {"status":401,"title":"Unauthorized","detail":"The server application intentionally responded with an HTTP error response status. The 'title' field contains the description of the status code. The value of the 'instance' field (if present) might help identify the circumstances of the problem.","instance":"4b6d16f42cf5cadc"}. Error: Deleting the file at [https://storage.dev-2-3.inrupt.com/04c44f1c-647d-447d-a5a9-2c44a66470ff/f272057d-47ac-4d7c-a436-bc6c47a4e76e] failed: [401] [Unauthorized] {"status":401,"title":"Unauthorized","detail":"The server application intentionally responded with an HTTP error response status. The 'title' field contains the description of the status code. The value of the 'instance' field (if present) might help identify the circumstances of the problem.","instance":"d71fb605a081a08b"}. Error: Deleting the file at [https://storage.dev-2-3.inrupt.com/04c44f1c-647d-447d-a5a9-2c44a66470ff/f272057d-47ac-4d7c-a436-bc6c47a4e76e] failed: [401] [Unauthorized] {"status":401,"title":"Unauthorized","detail":"The server application intentionally responded with an HTTP error response status. The 'title' field contains the description of the status code. The value of the 'instance' field (if present) might help identify the circumstances of the problem.","instance":"5ba56c2ba79cfe8d"}. Error: Deleting the file at [https://storage.dev-2-3.inrupt.com/04c44f1c-647d-447d-a5a9-2c44a66470ff/f272057d-47ac-4d7c-a436-bc6c47a4e76e] failed: [401] [Unauthorized] {"status":401,"title":"Unauthorized","detail":"The server application intentionally responded with an HTTP error response status. The 'title' field contains the description of the status code. The value of the 'instance' field (if present) might help identify the circumstances of the problem.","instance":"d996a5fca4d08eb3"}. Error: Deleting the file at [https://storage.dev-2-3.inrupt.com/04c44f1c-647d-447d-a5a9-2c44a66470ff/f272057d-47ac-4d7c-a436-bc6c47a4e76e] failed: [401] [Unauthorized] {"status":401,"title":"Unauthorized","detail":"The server application intentionally responded with an HTTP error response status. The 'title' field contains the description of the status code. The value of the 'instance' field (if present) might help identify the circumstances of the problem.","instance":"6fe822fb702e85db"}. at retryAsync (e2e/browser/solid-client-authn-browser/test/fixtures.ts:108:9) at tearDownPod (e2e/browser/solid-client-authn-browser/test/fixtures.ts:345:3) at Object.<anonymous> (e2e/node/server/e2e-app-test.spec.ts:168:5)
e2e-node (ESS Dev-2-3, true, ubuntu-latest, .nvmrc)
The operation was canceled.
e2e-node (ubuntu-latest, 18.x, ESS Dev-2-2, false)
Canceling since a higher priority waiting request for 'End-to-end node tests-refs/heads/exp/node-e2e' exists
e2e-node (ubuntu-latest, 18.x, ESS Dev-2-2, false)
The operation was canceled.
e2e-node (ubuntu-latest, 20.x, ESS PodSpaces, false)
Canceling since a higher priority waiting request for 'End-to-end node tests-refs/heads/exp/node-e2e' exists
e2e-node (ubuntu-latest, 20.x, ESS PodSpaces, false)
The operation was canceled.
e2e-node (ubuntu-latest, 18.x, ESS PodSpaces, false)
Canceling since a higher priority waiting request for 'End-to-end node tests-refs/heads/exp/node-e2e' exists
e2e-node (ubuntu-latest, 18.x, ESS PodSpaces, false)
The operation was canceled.
RETRY 1: RP initiated login/out using playwright › Should be able to login and out using oidc: e2e/node/server/e2e-browser-script.spec.ts#L82
thrown: "Exceeded timeout of 120000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at e2e/node/server/e2e-browser-script.spec.ts:82:5 at Object.<anonymous> (e2e/node/server/e2e-browser-script.spec.ts:55:9)
RETRY 1: Testing against express app with session keep alive off › Should be able to properly login and out with idp logout: e2e/node/server/e2e-app-test.spec.ts#L75
locator.fill: Timeout 30000ms exceeded. Call log: - waiting for getByRole('textbox', { name: 'Username' }) at CognitoPage.login (node_modules/@inrupt/internal-playwright-helpers/dist/index.js:38:14) at performTest (e2e/node/server/e2e-app-test.spec.ts:75:21) at Object.<anonymous> (e2e/node/server/e2e-app-test.spec.ts:175:5)
RETRY 2: Testing against express app with session keep alive off › Should be able to properly login and out with idp logout: e2e/node/server/e2e-app-test.spec.ts#L75
locator.fill: Timeout 30000ms exceeded. Call log: - waiting for getByRole('textbox', { name: 'Username' }) at CognitoPage.login (node_modules/@inrupt/internal-playwright-helpers/dist/index.js:38:14) at performTest (e2e/node/server/e2e-app-test.spec.ts:75:21) at Object.<anonymous> (e2e/node/server/e2e-app-test.spec.ts:175:5)
RETRY 3: Testing against express app with session keep alive off › Should be able to properly login and out with idp logout: e2e/browser/solid-client-authn-browser/test/fixtures.ts#L206
Could not find links to the resource's ACR. at createClientResource (e2e/browser/solid-client-authn-browser/test/fixtures.ts:206:11) at seedPod (e2e/browser/solid-client-authn-browser/test/fixtures.ts:324:29) at Object.<anonymous> (e2e/node/server/e2e-app-test.spec.ts:161:16)
RETRY 4: Testing against express app with session keep alive off › Should be able to properly login and out with idp logout: e2e/browser/solid-client-authn-browser/test/fixtures.ts#L108
An async callback is still failing after 5 retries. The errors were: Error: Deleting the file at [https://storage.dev-2-3.inrupt.com/04c44f1c-647d-447d-a5a9-2c44a66470ff/f272057d-47ac-4d7c-a436-bc6c47a4e76e] failed: [401] [Unauthorized] {"status":401,"title":"Unauthorized","detail":"The server application intentionally responded with an HTTP error response status. The 'title' field contains the description of the status code. The value of the 'instance' field (if present) might help identify the circumstances of the problem.","instance":"e940042e5afed285"}. Error: Deleting the file at [https://storage.dev-2-3.inrupt.com/04c44f1c-647d-447d-a5a9-2c44a66470ff/f272057d-47ac-4d7c-a436-bc6c47a4e76e] failed: [401] [Unauthorized] {"status":401,"title":"Unauthorized","detail":"The server application intentionally responded with an HTTP error response status. The 'title' field contains the description of the status code. The value of the 'instance' field (if present) might help identify the circumstances of the problem.","instance":"a9fcb69259d13085"}. Error: Deleting the file at [https://storage.dev-2-3.inrupt.com/04c44f1c-647d-447d-a5a9-2c44a66470ff/f272057d-47ac-4d7c-a436-bc6c47a4e76e] failed: [401] [Unauthorized] {"status":401,"title":"Unauthorized","detail":"The server application intentionally responded with an HTTP error response status. The 'title' field contains the description of the status code. The value of the 'instance' field (if present) might help identify the circumstances of the problem.","instance":"e11452acf7924452"}. Error: Deleting the file at [https://storage.dev-2-3.inrupt.com/04c44f1c-647d-447d-a5a9-2c44a66470ff/f272057d-47ac-4d7c-a436-bc6c47a4e76e] failed: [401] [Unauthorized] {"status":401,"title":"Unauthorized","detail":"The server application intentionally responded with an HTTP error response status. The 'title' field contains the description of the status code. The value of the 'instance' field (if present) might help identify the circumstances of the problem.","instance":"3ef534561642c779"}. Error: Deleting the file at [https://storage.dev-2-3.inrupt.com/04c44f1c-647d-447d-a5a9-2c44a66470ff/f272057d-47ac-4d7c-a436-bc6c47a4e76e] failed: [401] [Unauthorized] {"status":401,"title":"Unauthorized","detail":"The server application intentionally responded with an HTTP error response status. The 'title' field contains the description of the status code. The value of the 'instance' field (if present) might help identify the circumstances of the problem.","instance":"f079be580fcd8763"}. at retryAsync (e2e/browser/solid-client-authn-browser/test/fixtures.ts:108:9) at tearDownPod (e2e/browser/solid-client-authn-browser/test/fixtures.ts:345:3) at Object.<anonymous> (e2e/node/server/e2e-app-test.spec.ts:168:5)