Skip to content
Build Application

ci: bump to solo linux large and auto retry setup node (#276) #92

Sign in to view logs

ci: bump to solo linux large and auto retry setup node (#276)

ci: bump to solo linux large and auto retry setup node (#276) #92

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

9 fail, 93 pass in 28m 0s

  1 files  ±0  11 suites  ±0   28m 0s ⏱️ - 1m 58s
102 tests ±0  93 ✅  -  6  0 💤 ±0  9 ❌ +6 
 83 runs   - 5  74 ✅  - 11  0 💤 ±0  9 ❌ +6 

Results for commit cc88508. ± Comparison against earlier commit cf33430.

Annotations

Check warning on line 0 in NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] add node4 to the network

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] add node4 to the network (NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] add node4 to the network) failed 

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

Received: [Error: expect(received).resolves.toBeTruthy()·
Received promise rejected instead of resolved
Rejected to value: [FullstackTestingError: Error in setting up nodes: node 'node0' is not FREEZE_COMPLETE [ attempt = 100/100 ]]]
    at Object.<anonymous> (/runner/_work/solo/solo/test/e2e/commands/node.test.mjs:155:19)

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 
Unexpected server response: 500
Unexpected server response: 500
Unexpected server response: 500
Unexpected server response: 500
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 19s]
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 PackageInstallerE2E fetchPlatform should fail with invalid tag

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

PackageInstallerE2E fetchPlatform should fail with invalid tag (PackageInstallerE2E fetchPlatform should fail with invalid tag) 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/core/platform_installer_e2e.test.mjs:63: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/core/platform_installer_e2e.test.mjs:45: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/core/platform_installer_e2e.test.mjs:29: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(1)

Expected one assertion to be called but received zero assertion calls.
    at Object.<anonymous> (/runner/_work/solo/solo/test/e2e/core/platform_installer_e2e.test.mjs:64: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 PackageInstallerE2E copyTLSKeys should succeed to copy TLS keys for node0

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

PackageInstallerE2E copyTLSKeys should succeed to copy TLS keys for node0 (PackageInstallerE2E copyTLSKeys should succeed to copy TLS keys for node0) failed 

junit-e2e.xml [took 5s]
Raw output 
Error: thrown: "Exceeded timeout of 5000 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/core/platform_installer_e2e.test.mjs:145: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/core/platform_installer_e2e.test.mjs:144: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/core/platform_installer_e2e.test.mjs:29: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 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 10s]
Raw output 
Error: thrown: "Exceeded timeout of 10000 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/core/platform_installer_e2e.test.mjs:165: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/core/platform_installer_e2e.test.mjs:164: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/core/platform_installer_e2e.test.mjs:29: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 K8 should be able to port forward gossip port

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

K8 should be able to port forward gossip port (K8 should be able to port forward gossip port) failed 

junit-e2e.xml [took 5s]
Raw output 
Error: thrown: "Exceeded timeout of 5000 ms for a test while waiting for `done()` to be called.
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/core/k8_e2e.test.mjs:96: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/core/k8_e2e.test.mjs:27: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 RelayCommand 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

RelayCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with network deploy (RelayCommand 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/relay.test.mjs:52: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/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)

Check notice on line 0 in .github

See this annotation in the file changed.

@github-actions github-actions / E2E Test Results

102 tests found 

There are 102 tests, see "Raw output" for the full list of tests.
Raw output 
AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should cleanup previous deployment ‑ AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should cleanup previous deployment
AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with network deploy ‑ AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with network deploy
AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node setup command ‑ AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node setup command
AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node start command ‑ AccountCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node start command
AccountCommand account create/update command should be able to get account-1 ‑ AccountCommand account create/update command should be able to get account-1
AccountCommand account create/update command should be able to get account-2 ‑ AccountCommand account create/update command should be able to get account-2
AccountCommand account create/update command should create account with ecdsa private key and set alias ‑ AccountCommand account create/update command should create account with ecdsa private key and set alias
AccountCommand account create/update command should create account with no options ‑ AccountCommand account create/update command should create account with no options
AccountCommand account create/update command should create account with private key and hbar amount options ‑ AccountCommand account create/update command should create account with private key and hbar amount options
AccountCommand account create/update command should update account-1 ‑ AccountCommand account create/update command should update account-1
AccountCommand account create/update command should update account-2 with accountId, amount, new private key, and standard out options ‑ AccountCommand account create/update command should update account-2 with accountId, amount, new private key, and standard out options
AccountCommand account init command should succeed with init command ‑ AccountCommand account init command should succeed with init command
AccountCommand account init command special accounts should have new keys account 3 should not have genesis key ‑ AccountCommand account init command special accounts should have new keys account 3 should not have genesis key
AccountCommand account init command special accounts should have new keys account 4 should not have genesis key ‑ AccountCommand account init command special accounts should have new keys account 4 should not have genesis key
AccountCommand account init command special accounts should have new keys account 5 should not have genesis key ‑ AccountCommand account init command special accounts should have new keys account 5 should not have genesis key
AccountCommand node proxies should be UP proxy should be UP: node0  ‑ AccountCommand node proxies should be UP proxy should be UP: node0 
AccountCommand node proxies should be UP proxy should be UP: node1  ‑ AccountCommand node proxies should be UP proxy should be UP: node1 
AccountCommand node proxies should be UP proxy should be UP: node2  ‑ AccountCommand node proxies should be UP proxy should be UP: node2 
AccountManager should be able to load a new client ‑ AccountManager should be able to load a new client
AccountManager should be able to stop port forwards ‑ AccountManager should be able to stop port forwards
ChartManager should be able to check if a chart is installed ‑ ChartManager should be able to check if a chart is installed
ChartManager should be able to list installed charts ‑ ChartManager should be able to list installed charts
ClusterCommand function getClusterInfo should return true ‑ ClusterCommand function getClusterInfo should return true
ClusterCommand function showClusterList should return right true ‑ ClusterCommand function showClusterList should return right true
ClusterCommand function showInstalledChartList should return right true ‑ ClusterCommand function showInstalledChartList should return right true
ClusterCommand should cleanup existing deployment ‑ ClusterCommand should cleanup existing deployment
ClusterCommand solo cluster reset should fail with invalid cluster name ‑ ClusterCommand solo cluster reset should fail with invalid cluster name
ClusterCommand solo cluster reset should work with valid args ‑ ClusterCommand solo cluster reset should work with valid args
ClusterCommand solo cluster setup should fail with invalid cluster name ‑ ClusterCommand solo cluster setup should fail with invalid cluster name
ClusterCommand solo cluster setup should work with valid args ‑ ClusterCommand solo cluster setup should work with valid args
K8 should be able to cat a log file inside the container ‑ K8 should be able to cat a log file inside the container
K8 should be able to check if a path is directory inside a container ‑ K8 should be able to check if a path is directory inside a container
K8 should be able to copy a file to and from a container ‑ K8 should be able to copy a file to and from a container
K8 should be able to create and delete a namespaces ‑ K8 should be able to create and delete a namespaces
K8 should be able to detect cluster IP ‑ K8 should be able to detect cluster IP
K8 should be able to detect pod IP of a pod ‑ K8 should be able to detect pod IP of a pod
K8 should be able to list clusters ‑ K8 should be able to list clusters
K8 should be able to list contexts ‑ K8 should be able to list contexts
K8 should be able to list namespaces ‑ K8 should be able to list namespaces
K8 should be able to list persistent volume claims ‑ K8 should be able to list persistent volume claims
K8 should be able to port forward gossip port ‑ K8 should be able to port forward gossip port
K8 should be able to recycle pod by labels ‑ K8 should be able to recycle pod by labels
K8 should be able to run wait for pod conditions ‑ K8 should be able to run wait for pod conditions
K8 should be able to run wait for pod ready ‑ K8 should be able to run wait for pod ready
K8 should be able to run wait for pod ‑ K8 should be able to run wait for pod
MirrorNodeCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should cleanup previous deployment ‑ MirrorNodeCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should cleanup previous deployment
MirrorNodeCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with network deploy ‑ MirrorNodeCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with network deploy
MirrorNodeCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node setup command ‑ MirrorNodeCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node setup command
MirrorNodeCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node start command ‑ MirrorNodeCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node start command
MirrorNodeCommand mirror node api and hedera explorer should success ‑ MirrorNodeCommand mirror node api and hedera explorer should success
MirrorNodeCommand mirror node deploy should success ‑ MirrorNodeCommand mirror node deploy should success
MirrorNodeCommand mirror node destroy should success ‑ MirrorNodeCommand mirror node destroy should success
NetworkCommand network deploy command should succeed ‑ NetworkCommand network deploy command should succeed
NetworkCommand network destroy should success ‑ NetworkCommand network destroy should success
NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should cleanup previous deployment ‑ NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should cleanup previous deployment
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
NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node setup command ‑ NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node setup command
NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node start command ‑ NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node start command
NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should cleanup previous deployment ‑ NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should cleanup previous deployment
NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with network deploy ‑ NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with network deploy
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
NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node start command ‑ NodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node start command
NodeCommand Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Account creation should succeed ‑ NodeCommand Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Account creation should succeed
NodeCommand Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed ‑ NodeCommand Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed
NodeCommand Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Node Proxy should be UP [mode kill, release v0.49.0-alpha.2, keyFormat: pfx ‑ NodeCommand Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Node Proxy should be UP [mode kill, release v0.49.0-alpha.2, keyFormat: pfx
NodeCommand Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Account creation should succeed ‑ NodeCommand Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Account creation should succeed
NodeCommand Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed ‑ NodeCommand Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed
NodeCommand Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Node Proxy should be UP [mode stop, release v0.49.0-alpha.2, keyFormat: pem ‑ NodeCommand Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Node Proxy should be UP [mode stop, release v0.49.0-alpha.2, keyFormat: pem
NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Account creation should succeed ‑ NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Account creation should succeed
NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed ‑ NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed
NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 refresh should succeed ‑ NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 refresh should succeed
NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 should be running ‑ NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 should be running
NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 should not be ACTIVE ‑ NodeCommand Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 should not be ACTIVE
NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Account creation should succeed ‑ NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Account creation should succeed
NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed ‑ NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed
NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 refresh should succeed ‑ NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 refresh should succeed
NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 should be running ‑ NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 should be running
NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 should not be ACTIVE ‑ NodeCommand Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 should not be ACTIVE
NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] Account creation should succeed ‑ NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] Account creation should succeed
NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed ‑ NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed
NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] add node4 to the network ‑ NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] add node4 to the network
NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] existing nodes private keys should not have changed ‑ NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] existing nodes private keys should not have changed
NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] node4 should not exist ‑ NodeCommand Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pfx] node4 should not exist
NodeCommand [beforeAll - ERROR]: Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pem] Account creation should succeed ‑ NodeCommand [beforeAll - ERROR]: Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pem] Account creation should succeed
NodeCommand [beforeAll - ERROR]: Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed ‑ NodeCommand [beforeAll - ERROR]: Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed
NodeCommand [beforeAll - ERROR]: Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pem] add node4 to the network ‑ NodeCommand [beforeAll - ERROR]: Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pem] add node4 to the network
NodeCommand [beforeAll - ERROR]: Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pem] existing nodes private keys should not have changed ‑ NodeCommand [beforeAll - ERROR]: Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pem] existing nodes private keys should not have changed
NodeCommand [beforeAll - ERROR]: Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pem] node4 should not exist ‑ NodeCommand [beforeAll - ERROR]: Should add a new node to the network [release v0.49.0-alpha.2, keyFormat: pem] node4 should not exist
PackageDownloaderE2E should succeed with a valid Hedera release tag ‑ PackageDownloaderE2E should succeed with a valid Hedera release tag
PackageInstallerE2E copyGossipKeys should succeed to copy legacy pfx gossip keys for node0 ‑ PackageInstallerE2E copyGossipKeys should succeed to copy legacy pfx gossip keys for node0
PackageInstallerE2E copyGossipKeys should succeed to copy pem gossip keys for node1 ‑ PackageInstallerE2E copyGossipKeys should succeed to copy pem gossip keys for node1
PackageInstallerE2E copyPlatformConfigFiles should succeed to copy platform config files for node0 ‑ PackageInstallerE2E copyPlatformConfigFiles should succeed to copy platform config files for node0
PackageInstallerE2E copyTLSKeys should succeed to copy TLS keys for node0 ‑ PackageInstallerE2E copyTLSKeys should succeed to copy TLS keys for node0
PackageInstallerE2E fetchPlatform should fail with invalid pod ‑ PackageInstallerE2E fetchPlatform should fail with invalid pod
PackageInstallerE2E fetchPlatform should fail with invalid tag ‑ PackageInstallerE2E fetchPlatform should fail with invalid tag
PackageInstallerE2E fetchPlatform should succeed with valid tag and pod ‑ PackageInstallerE2E fetchPlatform should succeed with valid tag and pod
PackageInstallerE2E prepareConfigTxt should succeed in generating config.txt ‑ PackageInstallerE2E prepareConfigTxt should succeed in generating config.txt
RelayCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should cleanup previous deployment ‑ RelayCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should cleanup previous deployment
RelayCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with network deploy ‑ RelayCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with network deploy
RelayCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node setup command ‑ RelayCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node setup command
RelayCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node start command ‑ RelayCommand Bootstrap network for test [release v0.47.0-alpha.0, keyFormat: pem] should succeed with node start command
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
View more details on GitHub Actions