Skip to content
This repository has been archived by the owner on Jan 16, 2020. It is now read-only.

cli arguments failing to be recognized #117

Open
saundersconsult opened this issue Feb 12, 2019 · 3 comments
Open

cli arguments failing to be recognized #117

saundersconsult opened this issue Feb 12, 2019 · 3 comments

Comments

@saundersconsult
Copy link

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):

  • OS: Windows Pro 10 - 1809 (Build 17763.253) 64-bit
  • Browser Version 72.0.3626.96 (Official Build) (64-bit), IE v 11.253.17763.0 Update Version: 11.0.105 (KB4480965)
  • Version [e.g. 22] ???

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

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@zpeters
Copy link
Owner

zpeters commented Feb 12, 2019

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
Copy link
Author

saundersconsult commented Feb 13, 2019 via email

@realpg
Copy link

realpg commented Jul 7, 2019

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants