[Fuego] [PATCH] iperf3: adjust versions in test.yaml file

Tim.Bird at sony.com Tim.Bird at sony.com
Wed Mar 7 19:48:35 UTC 2018

Here's a patch adding some clarity to the 'version' and 'fuego_release' fields
of the test.yaml file.

I decided these fields needed some documentation, so I added some
information to the following page:

I'm not sure if maintaining the fuego_release will get to be an onerous
task or not.  But it will be helpful to have something to distinguish
results from the same base test, but run under different conditions due to changes
in the fuego meta-materials (fuego_test.sh or spec.json).

The version field is for the base test, which currently is 3.1.3.
The fuego_release is the 'version' of the Fuego materials for this
test, which is currently '1'.  As we change Fuego test materials,
we will want to increment this number, to reflect that the test
has changed (change in building, execution, parsing, etc.) so that
we aren't comparing apples to oranges when we put test result data
on a central test repository.

Signed-off-by: Tim Bird <tim.bird at sony.com>
 engine/tests/Benchmark.iperf3/test.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/engine/tests/Benchmark.iperf3/test.yaml b/engine/tests/Benchmark.iperf3/test.yaml
index a11fd83..f95d8c1 100644
--- a/engine/tests/Benchmark.iperf3/test.yaml
+++ b/engine/tests/Benchmark.iperf3/test.yaml
@@ -9,8 +9,8 @@ author: |
     Mark Ashley, Aaron Brown, Aeneas Jaißle, Susant Sahani, Bruce Simpson,
     Brian Tierney.
 maintainer: Daniel Sangorrin <daniel.sangorrin at toshiba.co.jp>
-version: 0.1
-fuego_release: 1.2.1
+version: 3.1.3
+fuego_release: 1
 type: Benchmark
 tags: ['network', 'performance']
 tarball_src: https://iperf.fr/download/source/iperf-3.1.3-source.tar.gz

More information about the Fuego mailing list