Current Behavior
When investigating #1491 i discovered this,
after running this:
PYTHONHASHSEED=2363631198 ./9pm/9pm.py -a case/containers/phys/test.py
PYTHONHASHSEED=2363631198 ./9pm/9pm.py -a case/containers/veth/test.py
The container created from the first test is still live, and interface e2 does still belongs to it, causing cascading faults:
admin@test-00-04-00:/> show container
NAME STATUS NETWORK MEMORY (KiB) CPU%
web-br0-veth Created web-br0-veth - 0.0
web-phys Up 5 minutes e2 72 0.01
admin@test-00-04-00:/>
Unsure if this is the failure that cause #1491, but i have seen all those tests also runs on the same dut (dut4) with this PYTHONHASH
Expected Behavior
First container removed
Steps To Reproduce
No response
Additional information
No response
Current Behavior
When investigating #1491 i discovered this,
after running this:
The container created from the first test is still live, and interface e2 does still belongs to it, causing cascading faults:
Unsure if this is the failure that cause #1491, but i have seen all those tests also runs on the same dut (dut4) with this PYTHONHASH
Expected Behavior
First container removed
Steps To Reproduce
No response
Additional information
No response