Flent-users discussion archives
 help / color / mirror / Atom feed
From: Erik Taraldsen <eriktar@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: flent-users@flent.org
Subject: [Flent-users] Re: Aggregate test results
Date: Tue, 9 Aug 2022 15:23:04 +0200	[thread overview]
Message-ID: <CAD-Tc1fjA4Jj1R022osasJO6_MQZ22d2X_V9wEiqEnttg2iyWg@mail.gmail.com> (raw)
In-Reply-To: <87zggd8vk0.fsf@toke.dk>

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

On Tue, Aug 9, 2022 at 2:12 PM Toke Høiland-Jørgensen <toke@toke.dk> wrote:

>
> So the way I usually do this is to drive all the client tests from a
> single Flent instance. There are two ways to do this: Run Flent on the
> server and connect to each client, running the test "in reverse", so to
> speak - the --swap-up-down parameter is meant specifically for this.
>
> The alternative is to use the remote execution features of Flent to
> start the test binaries on the clients using ssh (works best using a
> dedicated control network). This is what the --remote-host parameter is
> for.
>
> The benefit of driving everything in one test is that this way Flent
> also takes care of synchronising the data series into a single run
> (assuming clocks are reasonably synchronised across machines when using
> --remote-host), and you'll get everything in one data file. It can be a
> bit fiddly to set up, but you can encode everything into a single batch
> file so repetitions are easy...
>
>
 That don't fit snuggly into the test workflow I have set up.  But I'll
have a go at it.  Better to redo it now before we have started the testing
propper.

-Erik

[-- Attachment #2: Type: text/html, Size: 1542 bytes --]

      reply	other threads:[~2022-08-09 13:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 12:41 [Flent-users] " Erik Taraldsen
2022-08-08 11:55 ` [Flent-users] " Toke Høiland-Jørgensen
2022-08-09 11:56   ` Erik Taraldsen
2022-08-09 12:12     ` Toke Høiland-Jørgensen
2022-08-09 13:23       ` Erik Taraldsen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAD-Tc1fjA4Jj1R022osasJO6_MQZ22d2X_V9wEiqEnttg2iyWg@mail.gmail.com \
    --to=eriktar@gmail.com \
    --cc=flent-users@flent.org \
    --cc=toke@toke.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox