From: "Klatsky, Carl" <Carl_Klatsky@comcast.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>,
bloat <bloat@lists.bufferbloat.net>,
"flent-users@flent.org" <flent-users@flent.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>,
"make-wifi-fast@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] [Cake] flent testers wanted prior to next release
Date: Mon, 27 Feb 2017 21:42:33 -0000 [thread overview]
Message-ID: <c0c3899fae4540b9b80f60202c9b7de5@PACDCEX43.cable.comcast.com> (raw)
In-Reply-To: <87o9yni63z.fsf@toke.dk>
Toke,
Sorry for the delays again but I was able to turn on debug logging. I created an Issue on github Flent as the means to pass the debug log file. Please check there and we can continue the debug dialog there as needed.
Regards,
Carl Klatsky
-----Original Message-----
From: Toke Høiland-Jørgensen [mailto:toke@toke.dk]
Sent: Tuesday, January 31, 2017 10:47 AM
To: Klatsky, Carl <Carl_Klatsky@cable.comcast.com>
Cc: Dave Taht <dave.taht@gmail.com>; bloat <bloat@lists.bufferbloat.net>; flent-users@flent.org; cerowrt-devel@lists.bufferbloat.net; cake@lists.bufferbloat.net; make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [Cake] flent testers wanted prior to next release
"Klatsky, Carl" <Carl_Klatsky@comcast.com> writes:
> Finally had some time to get to this request. I downloaded the current
> git version of Flent and was able to launch the flent-gui on Windows.
> I had some old test *.flent.gz results files which loaded just fine. I
> tried to open the test files that were linked from Pete Heist mail
> "[Cake] Flent results for point-to-point Wi-Fi on LEDE/OM2P-HS
> available". Those files did not load for some reason.
>
> Note, in Windows I am only using Flent to view results files in the
> GUI. I do not use it to launch tests from Windows.
It would be helpful if you could turn on debug logging and exception debugging in the GUI, or run with -L logfile.txt from the command line, and post the resulting log entries (after trying to load the files that didn't work) somewhere... :)
-Toke
next prev parent reply other threads:[~2017-02-27 21:42 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 [this message]
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
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=c0c3899fae4540b9b80f60202c9b7de5@PACDCEX43.cable.comcast.com \
--to=carl_klatsky@comcast.com \
--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=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