You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a setup where bombardier is used by some script it is quite inconvenient to parse bombardier's output as it turned out (see #24). As a first step to resolve this issue, I plan to add two flags: --print (short: -p) and --no-print. The first one will control what to print in case something needs to be printed. Syntax will look something like:
--print=[<value>,]{1,2}<value><value> = intro (i) | progress (p) | result (r)
Some examples:
# prints intro, progress and result
bombardier --print=r,i,p <url># same as above
bombardier --print=intro,progress,result <url># result only
bombardier --print=r <url># same as above
bombardier -p=result <url>
In case you don't need any output, you will be able to use --no-print flag.
The text was updated successfully, but these errors were encountered:
Added --no-print flag, that allows to turn off the output completely.
-q is short for quiet, since kingpin allows short names to contain only
one letter and other letters (like -s and -n) are already in use.
Updates #24, updates #25.
codesenberg
changed the title
feature: flag to control output
feature: flags to control output
Feb 5, 2018
codesenberg
changed the title
feature: flags to control output
feature: flags to control the output
Feb 5, 2018
In a setup where bombardier is used by some script it is quite inconvenient to parse bombardier's output as it turned out (see #24). As a first step to resolve this issue, I plan to add two flags:
--print
(short:-p
) and--no-print
. The first one will control what to print in case something needs to be printed. Syntax will look something like:Some examples:
In case you don't need any output, you will be able to use
--no-print
flag.The text was updated successfully, but these errors were encountered: