-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Executed on MacOS Ventura 13.7.8.
Usually and weirdly the first execution runs successfully and the next ones fail. I could not figure out what the problem is. The error logs and SNM logs are included in the last commit.
[[https://github.com/SharedKnowledge/SharkNetMessenger/tree/master/basic_testing/testRuns]]
With the following command lists for four peers:
Peer A:
sendMessage CHAINLTX_filler_A.txt sn/file;echo sendMessage;openTCP 4444;echo openTCP;wait 500;block CHAINLTX_P1;wait 500;closeEncounter 1;wait 1000;echo closeEncounter;lsMessages 2;lsMessages 1;wait 1000;lsMessages 1;lsMessages 2;exit;
Peer B:
wait 3000;connectTCP localhost 4444;wait500;echo connectTCP;wait 500;release CHAINLTX_P1;echo release CHAINLTX_P1;wait 500;lsMessages;openTCP 4445;echo openTCP;wait 500;block CHAINLTX_P2;wait 1500;closeEncounter 1;echo closeEncounter 1;wait 500;lsMessages 2;lsMessages 1;wait 1000;lsMessages 1;lsMessages 2;exit;
Peer C:
wait 4500;connectTCP localhost 4445;wait500;echo connectTCP;wait 500;release CHAINLTX_P2;echo release CHAINLTX_P2;wait 500;lsMessages;openTCP 4446;echo openTCP;wait 500;block CHAINLTX_P3;wait 1500;closeEncounter 1;echo closeEncounter 1;wait 500;lsMessages 2;lsMessages 1;wait 1000;lsMessages 1;lsMessages 2;exit;
Peer D:
wait 6000;connectTCP localhost 4446;wait500;echo connectTCP;wait 500;release CHAINLTX_P3;echo release CHAINLTX_P3;wait 500;lsMessages;wait 1500;closeEncounter 1;echo closeEncounter 1;wait 500;lsMessages 2;lsMessages 1;wait 1000;lsMessages 1;lsMessages 2;exit;
I can't think of a fix