Add sleep after test with externally generated load
authorMichal Sojka <sojkam1@fel.cvut.cz>
Fri, 28 Aug 2009 07:31:12 +0000 (09:31 +0200)
committerMichal Sojka <sojkam1@fel.cvut.cz>
Fri, 28 Aug 2009 07:31:12 +0000 (09:31 +0200)
Even if the load generating process is killed, there are probably some
network packets queued for future sending and might influence future
test.

tests/ethflood.sh
tests/ethflood64k-w2.sh
tests/ethflood64k.sh
tests/ethload.sh
tests/ethloadsend.sh

index c54e0d0..b5c12dc 100755 (executable)
@@ -13,6 +13,7 @@ t() {
            kill $PID_S
        fi
        kill $PID_PING
+       sleep 1 # Wait for remote buffers to become empty
     done
 }
 
index dcda4e0..0cb2db6 100755 (executable)
@@ -13,6 +13,7 @@ t() {
            kill $PID_S
        fi
        kill $PID_PING
+       sleep 1 # Wait for remote buffers to become empty
     done
 }
 
index 98ea4fd..dcf1fe9 100755 (executable)
@@ -13,6 +13,7 @@ t() {
            kill $PID_S
        fi
        kill $PID_PING
+       sleep 1 # Wait for remote buffers to become empty
     done
 }
 
index fd6eaf7..c584b94 100755 (executable)
@@ -13,6 +13,7 @@ t() {
            kill $PID_S
        fi
        kill $PID_LOAD
+       sleep 1 # Wait for remote buffers to become empty
     done
 }
 
index 9ba99a8..1c41345 100755 (executable)
@@ -9,6 +9,7 @@ t() {
     vca_canping -m 1 -R FF:$RTPRIO -v -g $DRIVER -t 1 -d $CAN0 -w 0 -c $COUNT
     kill $PID_S
     kill %%  # Kill the whole pipe above
+    sleep 1 # Wait for ethernet buffers to become empty
 }