From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: ch <ch@ntrv.dk>
Cc: flent-users@flent.org
Subject: [Flent-users] Re: ERROR: Runner Burst 0 failed check: No command set for SilentProcessRunner
Date: Wed, 29 Mar 2023 14:33:06 +0200 [thread overview]
Message-ID: <878rffohz1.fsf@toke.dk> (raw)
In-Reply-To: <3a9e0bde-d5ea-32b1-f428-db22487a9cf6@ntrv.dk>
ch <ch@ntrv.dk> writes:
> On 29/03/2023 12.10, Toke Høiland-Jørgensen wrote:
>>> to run. Resulting in the node generating traffic for the full pipe for
>>> hours on end. My observation is the test does not terminate for unknown
>>> reasons.
>> Hmm, did you pull the latest version of traffic-gen? The version on
>> github had a bug where it would just go into an infinite loop and never
>> exit (and not produce any traffic either). Fixed that yesterday, so make
>> sure you pull the fixed version...
>
> Hmm. Good question
>
>> # ls -la traffic-gen
>> -rwxr-xr-x 1 root root 22832 Mar 28 20:04 traffic-gen
>
> I did compile the binary yesterday afternoon. So I can only assume it
> contains the tree commits from yesterday.
>
>> # git log --oneline
>> b316813 (HEAD -> master, origin/master, origin/HEAD) Use getrandom() instead of rand()/srand()
>> eedf705 Fix infinite loop in scheduling logic
>> 5c1007e Support setting the TOS byte on transmitted packets.
>
> (The application is missing the option for outputting a version number
> or git hash using e.g. -v, -V, or --version)
>
>> and not produce any traffic either
>
> It did produce *lots* of traffic. Had to terminate flent process to
> terminate the child traffic-gen processes.
> Attached is the graph of the network traffic levels (in MB/s) as
> reported by Proxmox.
Ah! Seems I introduced another infinite loop while fixing the previous
one; pushed another fix, please try that...
-Toke
next prev parent reply other threads:[~2023-03-29 12:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 12:20 [Flent-users] " Chriztoffer
2023-03-28 12:39 ` [Flent-users] " Toke Høiland-Jørgensen
2023-03-28 13:05 ` ch
2023-03-28 13:43 ` ch
2023-03-28 14:01 ` Toke Høiland-Jørgensen
2023-03-29 8:45 ` ch
2023-03-29 10:10 ` Toke Høiland-Jørgensen
2023-03-29 11:12 ` ch
2023-03-29 12:33 ` Toke Høiland-Jørgensen [this message]
2023-03-29 14:34 ` ch
2023-03-29 17:42 ` ch
2023-03-29 17:43 ` ch
2023-03-29 19:48 ` [Flent-users] Re: bursts test does not complete (WAS: ERROR: Runner Burst 0 failed check: No command set for SilentProcessRunner) ch
2023-03-29 22:10 ` Toke Høiland-Jørgensen
2023-03-30 8:37 ` ch
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=878rffohz1.fsf@toke.dk \
--to=toke@toke.dk \
--cc=ch@ntrv.dk \
--cc=flent-users@flent.org \
/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