search

zpeters / speedtest

Command line client for speedtest.net written in Go
GNU General Public License v3.0
370 stars 55 forks source link

cli arguments failing to be recognized #117

Open saundersconsult opened 5 years ago

saundersconsult commented 5 years ago

Describe the bug I am attempting to run the following binaries on Windows Pro 10 - 1809 (Build 17763.253) 64-bit. speedtest-64-v2.0.0-alpha.1-1-gbe80fe4 speedtest-64-2.0.0-a-2-g18a889d speedtest-32-2.0.0-a-2-g18a889d I get the same result. No matter which binary. All switches even help fail.

To Reproduce Steps to reproduce the behavior:

  1. speedtest-32-2.0.0-a-2-g18a889d.exe -h

  2. See the following (And I can replace the binary above with any of the 3 above or any argument.

  3. C:\bin>speedtest-32-2.0.0-a-2-g18a889d.exe -h Finding best server Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Ping test: ... Found best server: (1767) Atlanta, GA - Comcast Speedtest protocol version: 2.6 Ping test: .................... Download test: .................................... Upload test: ................................ --| Results |--- Ping results: 9 ms Download results: 336.294539 mbps Upload results: 153.792179 mbps

Expected behavior I would expect to see a list of servers, or with any other argument the appropriate responses, like help a list of commands.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Smartphone (please complete the following information): NA Using a PC

Additional context Add any other context about the problem here.

zpeters commented 5 years ago

This is my fault. The very latest compiled release is from the experimental branch. In that branch i have not progressed very far with the code. I'm still working on the basic measurements, then will add in the switches for feature parity with the current release.

The latest stable build is https://github.com/zpeters/speedtest/releases/tag/v1.0.5

saundersconsult commented 5 years ago

Hello Zach, Thanks this works great. You are doing fantastic work.

Shawn Saunders +1 (912) 665-6398 https://www.linkedin.com/in/srsaunders/

On Tue, Feb 12, 2019 at 8:48 AM Zach Peters notifications@github.com wrote:

This is my fault. The very latest compiled release is from the experimental branch. In that branch i have not progressed very far with the code. I'm still working on the basic measurements, then will add in the switches for feature parity with the current release.

The latest stable build is https://github.com/zpeters/speedtest/releases/tag/v1.0.5

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zpeters/speedtest/issues/117#issuecomment-462765610, or mute the thread https://github.com/notifications/unsubscribe-auth/AZlXYmew5Gjd51wJZmWsiYxCLQOge3O_ks5vMsYygaJpZM4a2Ve9 .

realpg commented 5 years ago

This is my fault. The very latest compiled release is from the experimental branch. In that branch i have not progressed very far with the code. I'm still working on the basic measurements, then will add in the switches for feature parity with the current release.

The latest stable build is https://github.com/zpeters/speedtest/releases/tag/v1.0.5

Can U make a new release with cli arguments?

Because the old 1.x versions have poor performance with big bandwidth, which is more than 2Gbps.

The new 2.x alpha version works fine, but cannot select server.

Thank U very much.