Skip to content
GitHub Actions / E2E Test Results failed May 8, 2024 in 0s

16 fail, 87 pass in 22m 33s

  1 files  11 suites   22m 33s ⏱️
103 tests 87 ✅ 0 💤 16 ❌
 66 runs  51 ✅ 0 💤 15 ❌

Results for commit 5de54e7.

Annotations

Check warning on line 0 in NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node setup command

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node setup command (NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node setup command) failed

junit-e2e.xml [took 2m 0s]
Raw output
Error: 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 it (/runner/_work/solo/solo/test/test_util.js:208:5)
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at describe (/runner/_work/solo/solo/test/test_util.js:178:3)
    at /runner/_work/solo/solo/test/e2e/commands/node.test.mjs:61:25
    at /runner/_work/solo/solo/node_modules/jest-each/build/bind.js:81:13
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/node_modules/jest-each/build/bind.js:47:15
    at Array.forEach (<anonymous>)
    at eachBind (/runner/_work/solo/solo/node_modules/jest-each/build/bind.js:39:22)
    at /runner/_work/solo/solo/test/e2e/commands/node.test.mjs:50:3
    at SourceTextModule.evaluate (node:internal/vm/module:229:23)
    at Runtime.linkAndEvaluateModule (/runner/_work/solo/solo/node_modules/jest-runtime/build/index.js:710:20)
    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:75:5)
    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)
Error: expect.assertions(1)

Expected one assertion to be called but received zero assertion calls.
    at Object.assertions (/runner/_work/solo/solo/test/test_util.js:209:14)
    at Promise.then.completed (/runner/_work/solo/solo/node_modules/jest-circus/build/utils.js:298:28)
    at new Promise (<anonymous>)
    at callAsyncCircusFn (/runner/_work/solo/solo/node_modules/jest-circus/build/utils.js:231:10)
    at _callCircusTest (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:316:40)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at _runTest (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:252:3)
    at _runTestsForDescribeBlock (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:126:9)
    at _runTestsForDescribeBlock (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:121:9)
    at _runTestsForDescribeBlock (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:121:9)
    at run (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:71:3)
    at runAndTransformResultsToJestFormat (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js:122:21)
    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:79:19)
    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)

Check warning on line 0 in NodeCommand Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

NodeCommand Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should suc…Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed) failed

junit-e2e.xml [took 1s]
Raw output
Error: expect(received).toBeNull()

Received: [Error: max attempts of 10 was reached for request with last error being: GrpcServiceError: Received RST_STREAM with code 0]
    at Object.<anonymous> (/runner/_work/solo/solo/test/e2e/commands/node.test.mjs:230:17)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Check warning on line 0 in NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 should not be ACTIVE

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 should not be ACTIVE (N…ommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 should not be ACTIVE) failed

junit-e2e.xml [took 20s]
Raw output
Unexpected server response: 500
Error: thrown: "Exceeded timeout of 20000 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 nodeShouldNotBeActive (/runner/_work/solo/solo/test/e2e/commands/node.test.mjs:264:3)
    at /runner/_work/solo/solo/test/e2e/commands/node.test.mjs:113:5
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/test/e2e/commands/node.test.mjs:94:3
    at /runner/_work/solo/solo/node_modules/jest-each/build/bind.js:81:13
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/node_modules/jest-each/build/bind.js:47:15
    at Array.forEach (<anonymous>)
    at eachBind (/runner/_work/solo/solo/node_modules/jest-each/build/bind.js:39:22)
    at /runner/_work/solo/solo/test/e2e/commands/node.test.mjs:50:3
    at SourceTextModule.evaluate (node:internal/vm/module:229:23)
    at Runtime.linkAndEvaluateModule (/runner/_work/solo/solo/node_modules/jest-runtime/build/index.js:710:20)
    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:75:5)
    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)

Check warning on line 0 in NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy (NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy) failed

junit-e2e.xml [took 2m 0s]
Raw output
Error: 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 it (/runner/_work/solo/solo/test/test_util.js:204:5)
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at describe (/runner/_work/solo/solo/test/test_util.js:178:3)
    at /runner/_work/solo/solo/test/e2e/commands/node.test.mjs:61:25
    at /runner/_work/solo/solo/node_modules/jest-each/build/bind.js:81:13
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/node_modules/jest-each/build/bind.js:47:15
    at Array.forEach (<anonymous>)
    at eachBind (/runner/_work/solo/solo/node_modules/jest-each/build/bind.js:39:22)
    at /runner/_work/solo/solo/test/e2e/commands/node.test.mjs:50:3
    at SourceTextModule.evaluate (node:internal/vm/module:229:23)
    at Runtime.linkAndEvaluateModule (/runner/_work/solo/solo/node_modules/jest-runtime/build/index.js:710:20)
    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:75:5)
    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)

Check warning on line 0 in NodeCommand Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

NodeCommand Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should suc…Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed) failed

junit-e2e.xml [took 1m 51s]
Raw output
Error: expect(received).toBeNull()

Received: [Error: max attempts of 10 was reached for request with last error being: GrpcServiceError: Received RST_STREAM with code 0]
    at Object.<anonymous> (/runner/_work/solo/solo/test/e2e/commands/node.test.mjs:230:17)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Check warning on line 0 in NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 refresh should succeed

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 refresh should succeed …mand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 refresh should succeed) failed

junit-e2e.xml [took 21s]
Raw output
Error: expect(received).toBeNull()

Received: [Error: expect(received).resolves.toBeTruthy()·
Received promise rejected instead of resolved
Rejected to value: [FullstackTestingError: Error in refreshing nodes: failed to copy gossip keys to pod 'network-node0-0': failed to copy files to pod 'network-node0-0': file does not exist: /home/runner/.solo/cache/v0.49/staging/v0.49.0-alpha.2/keys/s-private-node0.pem]]
    at Object.<anonymous> (/runner/_work/solo/solo/test/e2e/commands/node.test.mjs:255:17)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Check warning on line 0 in RelayCommand relay deploy and destroy should work with different number of relay nodes

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

1 out of 3 runs failed: RelayCommand relay deploy and destroy should work with different number of relay nodes (RelayCommand relay deploy and destroy should work with different number of relay nodes)

junit-e2e.xml [took 2m 0s]
Raw output
Error: 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 /runner/_work/solo/solo/node_modules/jest-each/build/bind.js:47:15
    at Array.forEach (<anonymous>)
    at eachBind (/runner/_work/solo/solo/node_modules/jest-each/build/bind.js:39:22)
    at /runner/_work/solo/solo/test/e2e/commands/relay.test.mjs:69:5
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/test/e2e/commands/relay.test.mjs:36:1
    at SourceTextModule.evaluate (node:internal/vm/module:229:23)
    at Runtime.linkAndEvaluateModule (/runner/_work/solo/solo/node_modules/jest-runtime/build/index.js:710:20)
    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:75:5)
    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)
Error: expect.assertions(2)

Expected two assertions to be called but received zero assertion calls.
    at /runner/_work/solo/solo/test/e2e/commands/relay.test.mjs:72:12
    at Object.<anonymous> (/runner/_work/solo/solo/node_modules/jest-each/build/bind.js:81:13)
    at Promise.then.completed (/runner/_work/solo/solo/node_modules/jest-circus/build/utils.js:298:28)
    at new Promise (<anonymous>)
    at callAsyncCircusFn (/runner/_work/solo/solo/node_modules/jest-circus/build/utils.js:231:10)
    at _callCircusTest (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:316:40)
    at _runTest (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:252:3)
    at _runTestsForDescribeBlock (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:126:9)
    at _runTestsForDescribeBlock (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:121:9)
    at run (/runner/_work/solo/solo/node_modules/jest-circus/build/run.js:71:3)
    at runAndTransformResultsToJestFormat (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js:122:21)
    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:79:19)
    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)

Check warning on line 0 in [afterAll - ERROR]: AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with network deploy

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

[afterAll - ERROR]: AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with net… AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with network deploy) failed

junit-e2e.xml [took 2m 0s]
Raw output
Error: 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 it (/runner/_work/solo/solo/test/test_util.js:204:5)
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at describe (/runner/_work/solo/solo/test/test_util.js:178:3)
    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:51:25
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:37:1
    at SourceTextModule.evaluate (node:internal/vm/module:229:23)
    at Runtime.linkAndEvaluateModule (/runner/_work/solo/solo/node_modules/jest-runtime/build/index.js:710:20)
    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:75:5)
    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)

Check warning on line 0 in [afterAll - ERROR]: AccountCommand node proxies should be UP proxy should be UP: node0

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

[afterAll - ERROR]: AccountCommand node proxies should be UP proxy should be UP: node0 ([afterAll - ERROR]: AccountCommand node proxies should be UP proxy should be UP: node0 ) failed

junit-e2e.xml [took 30s]
Raw output
Error: thrown: "Exceeded timeout of 30000 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 /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:67:7
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:64:3
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:37:1
    at SourceTextModule.evaluate (node:internal/vm/module:229:23)
    at Runtime.linkAndEvaluateModule (/runner/_work/solo/solo/node_modules/jest-runtime/build/index.js:710:20)
    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:75:5)
    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)

Check warning on line 0 in [afterAll - ERROR]: AccountCommand account init command should succeed with init command

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

[afterAll - ERROR]: AccountCommand account init command should succeed with init command ([afterAll - ERROR]: AccountCommand account init command should succeed with init command) failed

junit-e2e.xml [took 1s]
Raw output
FullstackTestingError: Error in creating account: Account keys updates failed for 4 accounts.
    at AccountCommand.init (/runner/_work/solo/solo/src/commands/account.mjs:211:13)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.<anonymous> (/runner/_work/solo/solo/test/e2e/commands/account.test.mjs:75:22)

Check warning on line 0 in [afterAll - ERROR]: AccountCommand account init command [afterAll - ERROR]: special accounts should have new keys account 3 should not have genesis key

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

[afterAll - ERROR]: AccountCommand account init command [afterAll - ERROR]: special accounts should have new keys account 3 sho…nd account init command [afterAll - ERROR]: special accounts should have new keys account 3 should not have genesis key) failed

junit-e2e.xml [took 20s]
Raw output
Error: thrown: "Exceeded timeout of 20000 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 /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:94:11
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:79:5
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:73:3
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:37:1
    at SourceTextModule.evaluate (node:internal/vm/module:229:23)
    at Runtime.linkAndEvaluateModule (/runner/_work/solo/solo/node_modules/jest-runtime/build/index.js:710:20)
    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:75:5)
    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)

Check warning on line 0 in [afterAll - ERROR]: AccountCommand account create/update command should create account with no options

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

[afterAll - ERROR]: AccountCommand account create/update command should create account with no options ([afterAll - ERROR]: AccountCommand account create/update command should create account with no options) failed

junit-e2e.xml [took 40s]
Raw output
Error: listen EADDRINUSE: address already in use 127.0.0.1:30213
    at Server.setupListenHandle [as _listen2] (node:net:1898:16)
    at listenInCluster (node:net:1946:12)
    at doListen (node:net:2116:7)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Error: listen EADDRINUSE: address already in use 127.0.0.1:30214
    at Server.setupListenHandle [as _listen2] (node:net:1898:16)
    at listenInCluster (node:net:1946:12)
    at doListen (node:net:2116:7)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Error: thrown: "Exceeded timeout of 40000 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 /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:110:5
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:107:3
    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)
    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)
    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:37:1
    at SourceTextModule.evaluate (node:internal/vm/module:229:23)
    at Runtime.linkAndEvaluateModule (/runner/_work/solo/solo/node_modules/jest-runtime/build/index.js:710:20)
    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:75:5)
    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)

Check warning on line 0 in Test execution failure: could be caused by test hooks like 'afterAll'.

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

All 2 runs failed: Test execution failure: could be caused by test hooks like 'afterAll'. ( Test execution failure: could be caused by test hooks like 'afterAll'.)

junit-e2e.xml [took 0s]
Raw output
{"message":"","stack":"Error: thrown: \"Exceeded timeout of 5000 ms for a hook.\nAdd 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.\"\n    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:88:7\n    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)\n    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)\n    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:79:5\n    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)\n    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)\n    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:73:3\n    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)\n    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)\n    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:37:1\n    at SourceTextModule.evaluate (node:internal/vm/module:229:23)\n    at Runtime.linkAndEvaluateModule (/runner/_work/solo/solo/node_modules/jest-runtime/build/index.js:710:20)\n    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:75:5)\n    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)\n    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)\nError: thrown: \"Exceeded timeout of 5000 ms for a hook.\nAdd 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.\"\n    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:58:3\n    at _dispatchDescribe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:91:26)\n    at describe (/runner/_work/solo/solo/node_modules/jest-circus/build/index.js:55:5)\n    at /runner/_work/solo/solo/test/e2e/commands/account.test.mjs:37:1\n    at SourceTextModule.evaluate (node:internal/vm/module:229:23)\n    at Runtime.linkAndEvaluateModule (/runner/_work/solo/solo/node_modules/jest-runtime/build/index.js:710:20)\n    at jestAdapter (/runner/_work/solo/solo/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:75:5)\n    at runTestInternal (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:367:16)\n    at runTest (/runner/_work/solo/solo/node_modules/jest-runner/build/runTest.js:444:34)"}

Check warning on line 0 in PackageInstallerE2E fetchPlatform should succeed with valid tag and pod

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

PackageInstallerE2E fetchPlatform should succeed with valid tag and pod (PackageInstallerE2E fetchPlatform should succeed with valid tag and pod) failed

junit-e2e.xml [took 11s]
Raw output
Unexpected server response: 500

Check warning on line 0 in PackageInstallerE2E copyPlatformConfigFiles should succeed to copy platform config files for node0

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

PackageInstallerE2E copyPlatformConfigFiles should succeed to copy platform config files for node0 (PackageInstallerE2E copyPlatformConfigFiles should succeed to copy platform config files for node0) failed

junit-e2e.xml [took 2s]
Raw output
Unexpected server response: 404

Check warning on line 0 in [afterAll - ERROR]: MirrorNodeCommand mirror node deploy should success

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

[afterAll - ERROR]: MirrorNodeCommand mirror node deploy should success ([afterAll - ERROR]: MirrorNodeCommand mirror node deploy should success) failed

junit-e2e.xml [took 2m 1s]
Raw output
Error: listen EADDRINUSE: address already in use 127.0.0.1:30212
    at Server.setupListenHandle [as _listen2] (node:net:1898:16)
    at listenInCluster (node:net:1946:12)
    at doListen (node:net:2116:7)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Unexpected server response: 404
Unexpected server response: 404
Unexpected server response: 404
Unexpected server response: 404
Error: expect(received).toBeNull()

Received: [Error: expect(received).resolves.toBeTruthy()·
Received promise rejected instead of resolved
Rejected to value: [FullstackTestingError: failed to stop port-forwarder [haproxy-node0-6969f76c77-hw8vg:50211 -> 127.0.0.1:30212]]]
    at Object.<anonymous> (/runner/_work/solo/solo/test/e2e/commands/mirror_node.test.mjs:82:17)