fix: bump platform version to v0.50.0

[jeromy-cannon]

Description

This pull request changes the following:

• bump platform version to v0.50.0

Related Issues

• Closes #

[github-actions]

Unit Test Results - Linux

  1 files  ±0   19 suites  ±0   1m 50s ⏱️ -16s
123 tests ±0  123 ✅ ±0  0 💤 ±0  0 ❌ ±0 
149 runs  ±0  149 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit aa18fbc. ± Comparison against base commit 0026118.

[github-actions]

Unit Test Results - Windows

  1 files  ±0   19 suites  ±0   1m 57s ⏱️ ±0s
123 tests ±0  123 ✅ ±0  0 💤 ±0  0 ❌ ±0 
149 runs  ±0  149 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit aa18fbc. ± Comparison against base commit 0026118.

[github-actions]

E2E Relay Tests Coverage Report

1 files  ±0  1 suites  ±0   3m 1s ⏱️ +20s
5 tests ±0  5 ✅ ±0  0 💤 ±0  0 ❌ ±0 
6 runs  ±0  6 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit aa18fbc. ± Comparison against base commit 0026118.

This pull request removes 4 and adds 4 tests. Note that renamed tests count towards both.

RelayCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should cleanup previous deployment ‑ RelayCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should cleanup previous deployment
RelayCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy ‑ RelayCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy
RelayCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node setup command ‑ RelayCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node setup command
RelayCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node start command ‑ RelayCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node start command

RelayCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should cleanup previous deployment ‑ RelayCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should cleanup previous deployment
RelayCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with network deploy ‑ RelayCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with network deploy
RelayCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node setup command ‑ RelayCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node setup command
RelayCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node start command ‑ RelayCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node start command

♻️ This comment has been updated with latest results.

[github-actions]

E2E Tests Coverage Report

55 tests  ±0   55 ✅ +1   3m 35s ⏱️ - 5m 36s
 9 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌  - 1 

Results for commit aa18fbc. ± Comparison against base commit 0026118.

This pull request removes 4 and adds 4 tests. Note that renamed tests count towards both.

AccountCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should cleanup previous deployment ‑ AccountCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should cleanup previous deployment
AccountCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy ‑ AccountCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy
AccountCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node setup command ‑ AccountCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node setup command
AccountCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node start command ‑ AccountCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node start command

AccountCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should cleanup previous deployment ‑ AccountCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should cleanup previous deployment
AccountCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with network deploy ‑ AccountCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with network deploy
AccountCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node setup command ‑ AccountCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node setup command
AccountCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node start command ‑ AccountCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node start command

[github-actions]

E2E Mirror Node Tests Coverage Report

11 tests  ±0   11 ✅ +2   4m 29s ⏱️ - 5m 12s
 1 suites ±0    0 💤  - 1 
 1 files   ±0    0 ❌  - 1 

Results for commit aa18fbc. ± Comparison against base commit 0026118.

This pull request removes 4 and adds 4 tests. Note that renamed tests count towards both.

MirrorNodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should cleanup previous deployment ‑ MirrorNodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should cleanup previous deployment
MirrorNodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy ‑ MirrorNodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy
MirrorNodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node setup command ‑ MirrorNodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node setup command
MirrorNodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node start command ‑ MirrorNodeCommand Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node start command

MirrorNodeCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should cleanup previous deployment ‑ MirrorNodeCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should cleanup previous deployment
MirrorNodeCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with network deploy ‑ MirrorNodeCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with network deploy
MirrorNodeCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node setup command ‑ MirrorNodeCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node setup command
MirrorNodeCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node start command ‑ MirrorNodeCommand Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node start command

[github-actions]

E2E Node Local Build Tests Coverage Report

8 tests  ±0   8 ✅ ±0   2m 58s ⏱️ - 1m 8s
2 suites ±0   0 💤 ±0 
1 files   ±0   0 ❌ ±0 

Results for commit aa18fbc. ± Comparison against base commit 0026118.

This pull request removes 8 and adds 8 tests. Note that renamed tests count towards both.

Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should cleanup previous deployment ‑ Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should cleanup previous deployment
Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with network deploy ‑ Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with network deploy
Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node setup command ‑ Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node setup command
Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node start command ‑ Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node start command
Node local build Node for platform app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should cleanup previous deployment ‑ Node local build Node for platform app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should cleanup previous deployment
Node local build Node for platform app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with network deploy ‑ Node local build Node for platform app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with network deploy
Node local build Node for platform app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node setup command ‑ Node local build Node for platform app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node setup command
Node local build Node for platform app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node start command ‑ Node local build Node for platform app should start successfully Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node start command

Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should cleanup previous deployment ‑ Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should cleanup previous deployment
Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with network deploy ‑ Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with network deploy
Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node setup command ‑ Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node setup command
Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node start command ‑ Node local build Node for hedera app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node start command
Node local build Node for platform app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should cleanup previous deployment ‑ Node local build Node for platform app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should cleanup previous deployment
Node local build Node for platform app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with network deploy ‑ Node local build Node for platform app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with network deploy
Node local build Node for platform app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node setup command ‑ Node local build Node for platform app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node setup command
Node local build Node for platform app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node start command ‑ Node local build Node for platform app should start successfully Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node start command

♻️ This comment has been updated with latest results.

[github-actions]

E2E Node PEM Stop Add Tests Coverage Report

 1 files  ±0   1 suites  ±0   9m 17s ⏱️ +6s
17 tests ±0  15 ✅ +1  1 💤 ±0  1 ❌  - 1 
19 runs  ±0  17 ✅ +2  1 💤  - 1  1 ❌  - 1 

For more details on these failures, see this check.

Results for commit aa18fbc. ± Comparison against base commit 0026118.

This pull request removes 17 and adds 17 tests. Note that renamed tests count towards both.

NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should cleanup previous deployment ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should cleanup previous deployment
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with network deploy
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node setup command ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node setup command
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node start command ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pem] should succeed with node start command
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Account creation should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Account creation should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Node should have started successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] 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 NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] 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 NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Account creation should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Account creation should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] Balance query should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 refresh should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] Node should refresh successfully [mode stop, release v0.49.0-alpha.2, keyFormat: pem] node0 refresh should succeed
…

NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pem] should cleanup previous deployment ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pem] should cleanup previous deployment
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with network deploy ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with network deploy
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node setup command ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node setup command
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node start command ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pem] should succeed with node start command
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should have started successfully [mode stop, release v0.50.0, keyFormat: pem] Account creation should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should have started successfully [mode stop, release v0.50.0, keyFormat: pem] Account creation should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should have started successfully [mode stop, release v0.50.0, keyFormat: pem] Balance query should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should have started successfully [mode stop, release v0.50.0, keyFormat: pem] Balance query should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should have started successfully [mode stop, release v0.50.0, keyFormat: pem] Node Proxy should be UP [mode stop, release v0.50.0, keyFormat: pem ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should have started successfully [mode stop, release v0.50.0, keyFormat: pem] Node Proxy should be UP [mode stop, release v0.50.0, keyFormat: pem
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should refresh successfully [mode stop, release v0.50.0, keyFormat: pem] Account creation should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should refresh successfully [mode stop, release v0.50.0, keyFormat: pem] Account creation should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should refresh successfully [mode stop, release v0.50.0, keyFormat: pem] Balance query should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should refresh successfully [mode stop, release v0.50.0, keyFormat: pem] Balance query should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should refresh successfully [mode stop, release v0.50.0, keyFormat: pem] node0 refresh should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Node should refresh successfully [mode stop, release v0.50.0, keyFormat: pem] node0 refresh should succeed
…

This pull request removes 1 skipped test and adds 1 skipped test. Note that renamed tests count towards both.

NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] 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 NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.49.0-alpha.2] 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 NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Should add a new node to the network [release v0.50.0, keyFormat: pem] existing nodes private keys should not have changed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pem, mode stop, keyFormat: pem, release v0.50.0] Should add a new node to the network [release v0.50.0, keyFormat: pem] existing nodes private keys should not have changed

♻️ This comment has been updated with latest results.

[github-actions]

E2E Node PFX Kill Add Tests Coverage Report

 1 files  ±0   1 suites  ±0   11m 21s ⏱️ - 1m 16s
17 tests ±0  15 ✅  - 2  1 💤 +1  1 ❌ +1 
19 runs  ±0  17 ✅  - 2  1 💤 +1  1 ❌ +1 

For more details on these failures, see this check.

Results for commit aa18fbc. ± Comparison against base commit 0026118.

This pull request removes 17 and adds 17 tests. Note that renamed tests count towards both.

NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should cleanup previous deployment ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should cleanup previous deployment
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with network deploy ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with network deploy
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node setup command ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node setup command
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node start command ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Bootstrap network for test [release v0.49.0-alpha.2, keyFormat: pfx] should succeed with node start command
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Account creation should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Account creation should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Node should have started successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] 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 NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] 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 NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Account creation should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Account creation should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] Balance query should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 refresh should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.49.0-alpha.2] Node should refresh successfully [mode kill, release v0.49.0-alpha.2, keyFormat: pfx] node0 refresh should succeed
…

NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pfx] should cleanup previous deployment ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pfx] should cleanup previous deployment
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with network deploy ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with network deploy
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node setup command ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node setup command
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node start command ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Bootstrap network for test [release v0.50.0, keyFormat: pfx] should succeed with node start command
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should have started successfully [mode kill, release v0.50.0, keyFormat: pfx] Account creation should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should have started successfully [mode kill, release v0.50.0, keyFormat: pfx] Account creation should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should have started successfully [mode kill, release v0.50.0, keyFormat: pfx] Balance query should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should have started successfully [mode kill, release v0.50.0, keyFormat: pfx] Balance query should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should have started successfully [mode kill, release v0.50.0, keyFormat: pfx] Node Proxy should be UP [mode kill, release v0.50.0, keyFormat: pfx ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should have started successfully [mode kill, release v0.50.0, keyFormat: pfx] Node Proxy should be UP [mode kill, release v0.50.0, keyFormat: pfx
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should refresh successfully [mode kill, release v0.50.0, keyFormat: pfx] Account creation should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should refresh successfully [mode kill, release v0.50.0, keyFormat: pfx] Account creation should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should refresh successfully [mode kill, release v0.50.0, keyFormat: pfx] Balance query should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should refresh successfully [mode kill, release v0.50.0, keyFormat: pfx] Balance query should succeed
NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should refresh successfully [mode kill, release v0.50.0, keyFormat: pfx] node0 refresh should succeed ‑ NodeCommand NodeCommand [testName node-cmd-e2e-pfx, mode kill, keyFormat: pfx, release v0.50.0] Node should refresh successfully [mode kill, release v0.50.0, keyFormat: pfx] node0 refresh should succeed
…

[JeffreyDallas]

Looks like node add test failed with similar symptom mentioned here
#308 (comment)

This newly added node stuck at CHECKING or BEHIND status

[jeromy-cannon]

Looks like node add test failed with similar symptom mentioned here #308 (comment)

This newly added node stuck at CHECKING or BEHIND status

@JeffreyDallas , no, not the same, I have a thread where I'm working on it:
https://swirldslabs.slack.com/archives/C03KD8K1XAS/p1717512658078859