Improved PROX cleanup when exiting

Sending now a 'quit' command to PROX, so that the thread running PROX in
an ssh session is now cleaned up correctly.
Also fixed a problem with the logging when running the code more than
once. We only create handlers now, when they do not yet exist.
Updated the rapid version.
Also added some more tests in the testcases.yaml for xtesting.
At the end of a run, the PROX.log files are copied in the results
directory.
The success criterium for a test 'pass_threshold' has been removed from
the test files and is to be controlled by the xtesting testcases.yaml
file.

Change-Id: Ifbbb1c91f32c9176f52025d9ae4c495b432a94c9
Signed-off-by: Luc Provoost <luc.provoost@intel.com>

1 files changed, 38 insertions, 5 deletions

diff --git a/VNFs/DPPD-PROX/helper-scripts/rapid/xtesting/testcases.yaml b/VNFs/DPPD-PROX/helper-scripts/rapid/xtesting/testcases.yaml
index 2db064f2..38ba1314 100644
--- a/VNFs/DPPD-PROX/helper-scripts/rapid/xtesting/testcases.yaml
+++ b/VNFs/DPPD-PROX/helper-scripts/rapid/xtesting/testcases.yaml
@@ -1,18 +1,51 @@
 ---
 tiers:
     -
-        name: rapid
+        name: IRQ_rapid_benchmarking
         order: 1
-        description: 'Rapid Testing'
+        description: 'IRQ Rapid Testing'
         testcases:
             -
-                case_name: rapid_tst009
+                case_name: rapid_irq
                 project_name: rapidxt
-                criteria: 100
+                criteria: 499500
+                # Criterium for irq is defined as 500000 -  the maximal allowed interrupt time per PMD loop (in us)
+                blocking: true
+                clean_flag: false
+                description: 'IRQ test'
+                run:
+                    name: rapidxt
+                    args:
+                        test_file: irq.test
+                        runtime: 5
+    -
+        name: TST009_rapid_benchmarking
+        order: 2
+        description: 'TST009 Rapid Testing'
+        testcases:
+            -
+                case_name: rapid_tst009_64b_64f
+                project_name: rapidxt
+                criteria: 0.5
+                # Criterium for TST009 testing is defined as the minimum packets per second received in the generator, expressed in Mpps
                 blocking: true
                 clean_flag: false
                 description: 'TST009 test, 64 byte packets, 64 flows'
                 run:
                     name: rapidxt
                     args:
-                        test_file: TST009_Throughput_64B_64F.test 
+                        test_file: TST009_Throughput_64B_64F.test
+                        runtime: 5
+            -
+                case_name: rapid_tst009_acaeab_16384f
+                project_name: rapidxt
+                criteria: 0.2
+                # Criterium for TST009 testing is defined as the minimum packets per second received in the generator, expressed in Mpps
+                blocking: true
+                clean_flag: false
+                description: 'TST009 test, imix acaeab, 16384 flows'
+                run:
+                    name: rapidxt
+                    args:
+                        test_file: TST009_Throughput_acaeab_16384F.test
+                        runtime: 5