[Fuego] [PATCH] iperf3: start the server when the container starts

Tim.Bird at sony.com Tim.Bird at sony.com
Tue Mar 20 03:51:04 UTC 2018


Sorry to get so behind in the patch review.

Looks good to me.  Applied.

My only worry is that we may end up with a lot of these extra services running.
But for now we only have netperf and iperf3 as persistent services, so let's
keep doing it this way until the overhead becomes a problem.

We should probably think about generic mechanisms for starting and stopping
services as they are required by tests (maybe using some form of reference counting).
As you noted, though, there can be races between multiple tests, so this is tricky.
 -- Tim

> -----Original Message-----
> From: Daniel Sangorrin on Thursday, March 08, 2018 9:31 PM
> 
> We start the iperf3 server here instead of in fuego_test.sh
> to avoid killing the server when the test finishes. Killing
> the server could cause race conditions for other boards
> waiting to run their iperf3 clients against it.
> 
> Signed-off-by: Daniel Sangorrin <daniel.sangorrin at toshiba.co.jp>
> ---
>  Dockerfile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Dockerfile b/Dockerfile
> index f918ff7..79bcfa3 100644
> --- a/Dockerfile
> +++ b/Dockerfile
> @@ -136,4 +136,4 @@ RUN DEBIAN_FRONTEND=noninteractive apt-get -yV
> install crossbuild-essential-armh
>  # Setup startup command
>  #
> ==========================================================
> ====================
> 
> -ENTRYPOINT service jenkins start && service netperf start && /bin/bash
> +ENTRYPOINT service jenkins start && service netperf start && iperf3 -V -s -D
> -f M && /bin/bash
> --
> 2.7.4
> 
> 
> _______________________________________________
> Fuego mailing list
> Fuego at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/fuego


More information about the Fuego mailing list