-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boomer支持locust的最新版本号是多少? #199
Comments
用 master 分支就好,一般是在 locust 做了不兼容的修改后,boomer 才会发一个 tag,让用户可以用回老版本的 locust。 |
多谢答复,使用新版本的解决了该问题。但是又出现了如下问题: locust侧: locust -V |
这个是因为握手的时候,没收到 locust 发回来 ack 信息。能稳定复现吗?我本地没复现。 |
locust版本早于2.10.0会出现这个问题。 |
可能是这个版本的 locust 还没加上 ack 消息。可以升级 locust 版本。 |
如何使用master分支呢,我试了一下go项目下go.mod只能填v1.6.0呢 |
在一个启用 go.mod 的项目,用这个命令试试 $ go get github.com/myzhan/boomer@master |
boomer执行./boomer --master-host=x.x.x.x --master-port=5557后,在locust出现如下报错:
[2023-12-13 00:54:57,425] C20231210173853.local/ERROR/locust.runners: An old (pre 2.0) worker tried to connect (server1.xxx.xxx). That's not going to work.
locust版本:2.19.1
boomer版本:v1.6.0
cat go.mod
module myproject
go 1.20
require (
github.com/asaskevich/EventBus v0.0.0-20200907212545-49d423059eef // indirect
github.com/go-ole/go-ole v1.3.0 // indirect
github.com/go-resty/resty/v2 v2.10.0 // indirect
github.com/google/uuid v1.4.0 // indirect
github.com/mattn/go-runewidth v0.0.15 // indirect
github.com/myzhan/boomer v1.6.0 // indirect
github.com/olekukonko/tablewriter v0.0.5 // indirect
github.com/rivo/uniseg v0.4.4 // indirect
github.com/shirou/gopsutil v3.21.11+incompatible // indirect
github.com/tklauser/go-sysconf v0.3.13 // indirect
github.com/tklauser/numcpus v0.7.0 // indirect
github.com/ugorji/go/codec v1.2.12 // indirect
github.com/yusufpapurcu/wmi v1.2.3 // indirect
github.com/zeromq/goczmq v4.1.0+incompatible // indirect
github.com/zeromq/gomq v0.0.0-20201031135124-cef4e507bb8e // indirect
github.com/zeromq/gomq/zmtp v0.0.0-20201031135124-cef4e507bb8e // indirect
golang.org/x/net v0.17.0 // indirect
golang.org/x/sys v0.15.0 // indirect
)
The text was updated successfully, but these errors were encountered: