You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently waitForBlock() and the other wait... methods use get info with exitOnFailure hardcoded to True. If the node hasn't finished enough of its startup to respond to get info the endpoint will be 404 and the whole test shuts down.
If the Node's popenProc is not None and killed is False, the wait... methods should tolerate 404 and other errors and retry, as long as popenProc tests good.
The text was updated successfully, but these errors were encountered:
bhazzard
changed the title
TestHarness wait... methods should be able to wait for a node to start
Tests: TestHarness wait... methods should be able to wait for a node to start
Sep 28, 2023
Currently
waitForBlock()
and the otherwait...
methods useget info
withexitOnFailure
hardcoded toTrue
. If the node hasn't finished enough of its startup to respond toget info
the endpoint will be 404 and the whole test shuts down.If the Node's
popenProc
is notNone
andkilled
is False, thewait...
methods should tolerate 404 and other errors and retry, as long aspopenProc
tests good.The text was updated successfully, but these errors were encountered: