We identified some tests (attached two examples) for which the code_pipeline (py.exe competition.py ...) gets stuck.
We noticed that the runtime gets stuck in beamngpy(version 1.24)/connection.py's _recv_exactly function (line 295) while waiting for some data from a TCP socket (connected to BeamNG). BeamNG process seems to exit after running the roads in the example files. A TCP connection is made to BeamNG, but nothing is received from TCP socket before it exits. We were suspecting it may have something to do with having short roads.
The example cases below can be run as standard test generators.
We identified some tests (attached two examples) for which the code_pipeline (py.exe competition.py ...) gets stuck.
We noticed that the runtime gets stuck in beamngpy(version 1.24)/connection.py's
_recv_exactly
function (line 295) while waiting for some data from a TCP socket (connected to BeamNG). BeamNG process seems to exit after running the roads in the example files. A TCP connection is made to BeamNG, but nothing is received from TCP socket before it exits. We were suspecting it may have something to do with having short roads.The example cases below can be run as standard test generators.
Case 1
Case 2