Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: YARDSTICK-1591
Change-Id: I3ea9039d25bfce578681adb9e27e1598e84a1f56
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
time.sleep was called in a number of classes which wasn't
mocked in the tests.
This accounted for 2.5 minutes of UT execution time.
The calls to time.sleep() have been mocked, and the test
execution time has been reduced.
JIRA: YARDSTICK-1595
Change-Id: I0a4f4962513cf8845471b074347601e33b35ef25
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
JIRA: YARDSTICK-1571
Cores in PROX support multiple configurations
NSB supports today the more basic one, i.e. [core x]
When one wants to use multiple cores sharing the same
configuration, instead of copying the whole [core]
section, PROX support the following syntax
[core x-y]
where x is the 1st core and y the last one
or (for instance) [core x,y,z]
NSB Now supports
[core a,b,c,d]
[core a-d]
[core a,c-d]
Change-Id: I34cd107143c89e16d58e7a99e1887ffbf720a5d1
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
|
|
JIRA: YARDSTICK-1524
Add dashboard, Traffic Profile support, PROX IRQ support, topology
Change-Id: I0c0cde66f4f4d3d25aa77c502bd4349cc1b3eca2
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
historical data
JIRA: YARDSTICK-1458
The TG is only sampled at the end of every test interval.
This is incorrect. It should be sampled every interval.
Change-Id: I612ead8a243a7d9930874d02adc9b959b843b99b
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
JIRA: YARDSTICK-1458
Removed excessive jitter by removing extra sleeps in start/stop/reset
ssh
Removed extra retries when bad data returned
Added a slep at end of test to give runner a chance to empty the queue
on shutdown
Added a timeout on port retry attempts
Change-Id: Ica60b11c7af242817a83c154157827581f60d16a
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
JIRA: YARDSTICK-1419
When using prox_binsearch algorithm, a binary search is
performed, increasing lower bound when step was successful
and decreasing upper bound when the step was a failure.
This runs until the test_precision (as specified in the
traffic profile) is reached. When the test precision
is reached, the test is not completed until the
runner duration is reached.
As runner duration is usually high (e.g. 1800sec), the
tests take much too long to execute.
This makes it difficult to create test suites.
Change-Id: I6cc503a09fb534a556c61c805e6df4786bb8cc4b
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
Removed unneeded output.
JIRA: YARDSTICK-1284
Change-Id: I41d9b8d2df417fa19b0a6f8c13bc9837dc3dde95
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
JIRA: YARDSTICK-1219
Currently NSB for NFVI using PROX returns sampling information every 13
seconds.
This is too slow.
It is required to return sampling information form Generator AND VNF at
least every 1 second.
This change is depandant on JIRA: YARDSTICK-1212 and YARDSTICK-1220
Change-Id: Ica7ab795a2919d191d8cd846d028e15739e33fb7
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
|
|
tVpeApproxVnf and TestProxSocketHelper classes mock "time.sleep" in
the setUp method without deleting it at the end of the test execution.
JIRA: YARDSTICK-1243
Change-Id: Iff31d9c7b400ad8a47f37792aeb0d20328b9d9e1
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
assertEqual(mock_xxx.call_count, 1) -> mock_xxx.assert_called_once
assertEqual(mock_xxx.call_count, 0) -> mock_xxx.assert_not_called
assertGreater(mock.call_count, 0) -> mock.assert_called()
assertGreaterEqual(mock.call_count, 1) -> mock.assert_called()
JIRA: YARDSTICK-1069
Change-Id: I890084d120c8e78304e169e2a0e5d30011a41525
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
* Fix pylint errors
* Add TODOs
Some errors are ignored locally, as they were a symptom of other problems.
These issues have been flagged with a TODO, and should be fixed later.
JIRA: YARDSTICK-837
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
Change-Id: I3d95537a64bde923703421510d27bac0d6dd92bd
|