Rocketmq metadata and test refactor#15834
Conversation
| container.start(); | ||
| try { | ||
| // Wait a bit for the broker to fully start | ||
| Thread.sleep(5000); |
There was a problem hiding this comment.
That's unfortunate. It would be nicer if there were a way to poll for readiness instead of blindly sleeping. Doesn't testcontainers have a mechanism for this?
There was a problem hiding this comment.
I did try and fix it using a Wait condition, trying to find some log that could be used, but there are several processes spun up, and i didn't have much success finding a good log. With that being said, I don't think we ever see this issue in CI, and i think the wackyness is only because im on ARM. I can back this piece out since it's not critical
breedx-splk
left a comment
There was a problem hiding this comment.
The metadata and move/refactor seem fine to me. I do hesitate to approve with a sleep in the tests...because I think that's a slippery slope that ends up slowing down an already slow test suite....but we can always circle back to that.
Part of #14096 and #14128
notes:
rocketmq:rocketmq-client:rocketmq-client-{version}) so I removed the redundantrocketmq-clientlevel.