Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Node Update tests fail with INVALID_NODE_ACCOUNT #855

Closed
nathanklick opened this issue Nov 20, 2024 · 1 comment · Fixed by #856
Closed

Node Update tests fail with INVALID_NODE_ACCOUNT #855

nathanklick opened this issue Nov 20, 2024 · 1 comment · Fixed by #856
Assignees
@nathanklick
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs Pending Triage New issue that needs to be triaged by the team released

Comments

@nathanklick
Copy link
Member

Describe the bug

Node Update tests are failing.

Describe the expected behavior

Node Update tests should succeed.

To Reproduce

  1. Run npm run build && npm run test-e2e-node-update

Additional Context

No response
@nathanklick nathanklick added Bug A error that causes the feature to behave differently than what was expected based on design docs Pending Triage New issue that needs to be triaged by the team labels Nov 20, 2024
@nathanklick nathanklick self-assigned this Nov 20, 2024
@nathanklick nathanklick mentioned this issue Nov 20, 2024
Merged
@JeffreyDallas JeffreyDallas mentioned this issue Nov 21, 2024
Closed
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.32.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nathanklick nathanklick

Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs Pending Triage New issue that needs to be triaged by the team released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: resolve node update test failures hashgraph/solo
2 participants
@nathanklick @swirlds-automation