From: Dave Taht <dave.taht@gmail.com>
To: flent-users <flent-users@flent.org>
Subject: [Flent-users] some breakages and a big test
Date: Sat, 10 Sep 2022 12:26:00 -0700 [thread overview]
Message-ID: <CAA93jw4p-9e5-fZdKdtZ45wMo30Jgj8MxWPrHtBPf=hG4YPoCw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
I've been working on a script that exercises some old tests. My goal
was to get something that ran
in under an hour that got a comprehensive viewpoint.
I'm terrible at python, so I do things in shell, rather than the batch facility.
Anyway, presently several of the more obscure tests break in
this...[1] but rather than describe which ones do,
I was wondering if folk around the world could modify the T variable
to reflect their connection type and post
the *.flent.gz files somewhere.
Having better error checking (like "is bbr available"), having it be
runnable on an osx box are longer term goals.
[1] ok, bursts_11e breaks, the ipv6 test breaks when no ipv6 is
present, the rrul-voip test breaks, the cisco flood test breaks
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
[-- Attachment #2: testall.sh --]
[-- Type: application/x-shellscript, Size: 4326 bytes --]
reply other threads:[~2022-09-10 19:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw4p-9e5-fZdKdtZ45wMo30Jgj8MxWPrHtBPf=hG4YPoCw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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