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
Been seeing timeouts in our integration tests. These timeouts appear to be caused by not shutting down the cluster of nodeos that are running. This PR #1182 moved shutdown of Cluster to a atexit.register call. Unfortunately, that is not called if a test exits due to an error or if os.exit() is called directly.
Seems we need to revert back to TestHarness.shutdown() calling Cluster.shutdown() instead of using atexit.register.
The text was updated successfully, but these errors were encountered:
Been seeing timeouts in our integration tests. These timeouts appear to be caused by not shutting down the cluster of nodeos that are running. This PR #1182 moved shutdown of
Cluster
to aatexit.register
call. Unfortunately, that is not called if a test exits due to an error or ifos.exit()
is called directly.Seems we need to revert back to
TestHarness.shutdown()
callingCluster.shutdown()
instead of usingatexit.register
.The text was updated successfully, but these errors were encountered: