hanzhenfang commented on issue #13267: URL: https://github.com/apache/apisix/issues/13267#issuecomment-4660195573
Hi, @Baoyuantop ,I looked through the failure pattern, and this does not look like a `limit-count` behavior failure. The failed assertions are from the generic Test::Nginx error-log guard: ```text pattern "[error]" should not match any line in error.log ``` The matched line is emitted by `lua-resty-events`: ```text worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed ``` In the pasted logs, that line appears next to old NGINX workers exiting and new workers starting. That points to the event broker Unix socket being closed during a test-server restart/reload. `lua-resty-events` reconnects after this, so the transient close is not necessarily fatal, but if the runtime logs it at `ngx.ERR`, APISIX tests fail because `[error]` appears in `error.log`. This matches the earlier APISIX discussion in #10550: during reload, the worker handling the Unix socket can be restarted, other workers temporarily lose the broker connection, and the practical CI impact is the log level. -- 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]
