dengliming commented on PR #6978: URL: https://github.com/apache/shenyu/pull/6978#issuecomment-5716076843
This is a good step forward, but I think we still need an explicit readiness check before sending the request. Right now we start the consumer and immediately issue the HTTP call, then wait for the log to appear. In CI, the flaky part seems to be that the route/logging path may not be fully ready yet when that request is sent, so we can still miss the log and time out even though RocketMQ itself is healthy. Could we split this into two phases? 1. wait until the gateway route is actually serving successfully 2. then send a fresh request and await the RocketMQ log for that request That would make the test assert “logging works after the system is ready” rather than depending on startup timing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
