chore(deps): bump jfrog/setup-jfrog-cli from 4.2.2 to 4.3.2 (#534) #229
GitHub Actions / E2E Node Update Tests Coverage Report
succeeded
Sep 4, 2024 in 0s
All 7 tests pass, 3 skipped in 2m 31s
Annotations
Check notice on line 0 in .github
github-actions / E2E Node Update Tests Coverage Report
3 skipped tests found
There are 3 skipped tests, see "Raw output" for the full list of skipped tests.
Raw output
Node update config.txt should be changed with new account id ‑ Node update config.txt should be changed with new account id
Node update should update a new node property successfully ‑ Node update should update a new node property successfully
Node update signing key and tls key should not match previous one ‑ Node update signing key and tls key should not match previous one
Check notice on line 0 in .github
github-actions / E2E Node Update Tests Coverage Report
10 tests found
There are 10 tests, see "Raw output" for the full list of tests.
Raw output
Node update Bootstrap network for test [release v0.53.2, keyFormat: pem] generate key files ‑ Node update Bootstrap network for test [release v0.53.2, keyFormat: pem] generate key files
Node update Bootstrap network for test [release v0.53.2, keyFormat: pem] should cleanup previous deployment ‑ Node update Bootstrap network for test [release v0.53.2, keyFormat: pem] should cleanup previous deployment
Node update Bootstrap network for test [release v0.53.2, keyFormat: pem] should succeed with network deploy ‑ Node update Bootstrap network for test [release v0.53.2, keyFormat: pem] should succeed with network deploy
Node update Bootstrap network for test [release v0.53.2, keyFormat: pem] should succeed with node setup command ‑ Node update Bootstrap network for test [release v0.53.2, keyFormat: pem] should succeed with node setup command
Node update Bootstrap network for test [release v0.53.2, keyFormat: pem] should succeed with node start command ‑ Node update Bootstrap network for test [release v0.53.2, keyFormat: pem] should succeed with node start command
Node update cache current version of private keys ‑ Node update cache current version of private keys
Node update config.txt should be changed with new account id ‑ Node update config.txt should be changed with new account id
Node update should succeed with init command ‑ Node update should succeed with init command
Node update should update a new node property successfully ‑ Node update should update a new node property successfully
Node update signing key and tls key should not match previous one ‑ Node update signing key and tls key should not match previous one
Loading