feat: report test progress under --debug - #124
Open
BKPepe wants to merge 1 commit into
Open
Conversation
--json, --csv and --simple suppress the spinner, so a run prints nothing between launch and the final result. --debug did not help: every existing debug call sits on an error path, so a run that succeeds stays quiet. Report each phase instead — server, IP info, ping, download, upload — with the timings, byte counts and stream settings the spinner cannot carry. Rates follow the run's own reporting mode, Mbps normally and MB/s under --bytes, so a debug line cannot contradict the result printed beside it. Nothing changes unless --debug is given.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
--json,--csvand--simplesuppress the spinner, so a run printsnothing between launch and the final result.
--debugdid not help — everyexisting debug call sits on an error path, so a run that succeeds stays
quiet.
This reports each phase with timings and byte counts:
Debug goes to stderr, so stdout stays clean for piping. Rates follow the
run's own mode — Mbps normally, MB/s under
--bytes— so a debug linecannot contradict the JSON beside it.
Nothing changes without
--debug. Tested against a live backend in--json,--simple --bytesand default modes.