From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] 4c09fa: lupin related hwtests
Date: Wed, 11 Jul 2012 10:53:36 -0700 [thread overview]
Message-ID: <4ffdbda071cab_b84f57ae49358b@sh2.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: 4c09fa67ae653d90ba7850998d92c4ee762df465
https://github.com/dtaht/deBloat/commit/4c09fa67ae653d90ba7850998d92c4ee762df465
Author: Dave Täht <dave.taht@bufferbloat.net>
Date: 2012-07-11 (Wed, 11 Jul 2012)
Changed paths:
A test/lupin/hwtest
A test/lupin/latency_under_load.org
A test/lupin/quantum.vars
A test/lupin/setup.vars
A test/lupin/testrun1.org
Log Message:
-----------
lupin related hwtests
I started at automating a string of tests to run nightly across
multiple servers across multiple paths. Natually I ended up with
far more variables than I'd planned for so I have to rethink
the test framework.
The nice thing is that these tests already thoroughly exposed
a major bug in VI/VO queue handling that is now fixed in openwrt mainline.
http://www.bufferbloat.net/issues/401
Which I have to get out to the 12 machines in the testbed...
reply other threads:[~2012-07-11 17:53 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ffdbda071cab_b84f57ae49358b@sh2.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@lists.bufferbloat.net \
/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