From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Dave Taht <dave.taht@gmail.com>,
cake@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net,
flent-users@flent.org,
"cerowrt-devel\@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] [Cake] flent testers wanted prior to next release
Date: Tue, 31 Jan 2017 17:58:09 +0100 [thread overview]
Message-ID: <8737fzi2u6.fsf@toke.dk> (raw)
In-Reply-To: <20170131085243.5d495e05@xeon-e3> (Stephen Hemminger's message of "Tue, 31 Jan 2017 08:52:43 -0800")
Stephen Hemminger <stephen@networkplumber.org> writes:
> On Tue, 31 Jan 2017 17:35:40 +0100
> Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>> Stephen Hemminger <stephen@networkplumber.org> writes:
>>
>> > On Tue, 20 Dec 2016 11:02:44 -0800
>> > Dave Taht <dave.taht@gmail.com> wrote:
>> >
>> > Has anyone automated or orchestrated flent? I would love to get several
>> > projects doing daily build flent runs. Both upstream kernel, net-next,
>> > and Intel Clear Linux has nightly build and test.
>>
>> Flent has a built-in batch mode that lets you automate running several
>> tests in a row including setup/teardown scripts etc... Is that what you
>> mean?
>
> That is start, was hoping someone had already done the nightly run
> kind of environment.
Ah, right. No, I think the main thing missing for that is some way to
collect the results that is a bit more systematic than just dumping data
files to disk... Have some ideas for that, but have not started writing
code yet; contributions welcome! ;)
-Toke
prev parent reply other threads:[~2017-01-31 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 19:02 [Cerowrt-devel] " Dave Taht
2016-12-20 20:20 ` Joel Wirāmu Pauling
2016-12-21 2:08 ` Aaron Wood
2016-12-21 11:02 ` [Cerowrt-devel] [Make-wifi-fast] " Jesper Dangaard Brouer
2016-12-21 2:06 ` [Cerowrt-devel] [Bloat] " Aaron Wood
2016-12-21 21:04 ` Dave Taht
2017-01-31 14:48 ` [Cerowrt-devel] [Cake] " Klatsky, Carl
2017-01-31 15:47 ` [Cerowrt-devel] [Make-wifi-fast] " Toke Høiland-Jørgensen
2017-02-27 21:42 ` Klatsky, Carl
2017-01-31 16:08 ` [Cerowrt-devel] " Stephen Hemminger
2017-01-31 16:35 ` [Cerowrt-devel] [Make-wifi-fast] " Toke Høiland-Jørgensen
2017-01-31 16:52 ` Stephen Hemminger
2017-01-31 16:58 ` Toke Høiland-Jørgensen [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.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737fzi2u6.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=flent-users@flent.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=stephen@networkplumber.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