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
Describe the bug
The near node crashes when running on the macos-latest platform within Github Actions workflow. The backtrace can be found in the workspaces-rs test branch. It's caused from PeerManagerActor::update_routing_table_trigger when calling into self.clock.now() - PRUNE_UNREACHABLE_PEERS_AFTER. This panic is only happening in Github Actions, and regularly works on the ubuntu instance of GithubActions, and also on a local macOS computer (x86 and M1).
To Reproduce
Run neard on Github Actions macos-latest. A crash should occur pointing PeerManagerActor::update_routing_table_trigger.
Additional context
Found related issue in rust-lang/rust#48980 where this panic is platform specific, so not sure if there's a straightforward solution to this.
The text was updated successfully, but these errors were encountered:
Describe the bug
The near node crashes when running on the
macos-latest
platform within Github Actions workflow. The backtrace can be found in the workspaces-rs test branch. It's caused fromPeerManagerActor::update_routing_table_trigger
when calling intoself.clock.now() - PRUNE_UNREACHABLE_PEERS_AFTER
. This panic is only happening in Github Actions, and regularly works on the ubuntu instance of GithubActions, and also on a local macOS computer (x86 and M1).To Reproduce
Run
neard
on Github Actions macos-latest. A crash should occur pointingPeerManagerActor::update_routing_table_trigger
.Or just fork off the branch from https://github.com/near/workspaces-rs/tree/test/non-deterministic-tests since that's already pulling in the nearcore binary with macos-latest.
Expected behavior
Does not crash the node with overflow
Version
Additional context
Found related issue in rust-lang/rust#48980 where this panic is platform specific, so not sure if there's a straightforward solution to this.
The text was updated successfully, but these errors were encountered: