Closed orthoxerox closed 6 years ago
Many thanks for reporting this. Could you confirm that fix that just landed on master actually resolves the issue?
I've never compiled a go program, so this might take a wee while.
Fortunately, it's very easy to do. First, you gonna need to download and install Go and then it's just (provided, you added go.exe
to your PATH
):
go get -u github.com/codesenberg/bombardier
(the binary will end up in %GOPATH%/bin
, I think)
Or, if you trust me enough, just use this version that I cross-compiled for windows/386 from master:
Hey, @orthoxerox, I was wondering if you had any progress with the issue.
Thanks for reminding me, I'll try and test it by the end of the week.
@orthoxerox, well, you haven't told by the end of which week I guess. According to average life expectancy, I will be physically able to wait for approx. 2000 weeks, but I'd rather not to :smile: So, any progress with this?
Sorry! Thanks for reminding me, I've transferred your build artifact to a location reachable from my work PC and will test tomorrow.
Hi! I've finally gotten around to testing the new version and I no longer get any panics from bombardier.
Hurray! :tada:
What version of bombardier are you using?
bombardier version v1.1.1 windows/386
What operating system and processor architecture are you using (if relevant)?
windows/386
What did you do?
bombardier -d 1m http://localhost:55555/test/00660066
What you expected to happen?
I expected it to run for 1 minute.
What actually happened?
This happens with no rhyme or reason I can detect. Sometimes it panics with
-d 1s
, sometimes it works for10s
with no issues.