This issue was introduced, because the LayerStack tests used, among other layers, the UDP4LinkLayer, which creates a socket and binds it to 0.0.0.0:<port>. The tests never use start_process and stop_process, thus the socket is never closed.
This fix works around this by simply using another type of layer, which does not bring this type of problem.
This issue was introduced, because the LayerStack tests used, among other layers, the UDP4LinkLayer, which creates a socket and binds it to
0.0.0.0:<port>. The tests never usestart_processandstop_process, thus the socket is never closed.This fix works around this by simply using another type of layer, which does not bring this type of problem.