-
Notifications
You must be signed in to change notification settings - Fork 117
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
Unable to connect to metrics listener in acceptance tests #1769
Comments
This seems to don't be in the current sprint but it can potentially make our next PRs to fail, having to restart, etc. This is a known issue even if we don't have the exact cause. What if we do the following in this sprint until we have more time to debug this:
|
Another option:
|
We have a lot of open CI failure tickets and bugs. Do you know how often this failure is happening right now? Whenever I see a CI failure, I add a note to the pull request, and include the ticket number for that CI failure. (Or I open a new CI failure ticket and tag it.) I don't see any PRs tagged with this bug. So maybe we don't need to do anything about it right now. Last time I saw this failure, I opened this ticket, and added more diagnostics to the test in PR #1770. So we need to wait for it to happen again. Then we might know how to fix it, or we might decide to disable it. |
Ah, I see that #1811 failed on Windows CI due to this bug. I'll go check the new logs and see if they help us decide what to do. |
This is actually a known issue in Windows Hyper-V, introduced by update KB4074588:
We can't use that workaround, but we can adjust the port range to exclude typically reserved ports (less than 53500).
As an added bonus, we'll be less likely to conflict with ephemeral ports on OSes that allocate them sequentially (macOS, Windows): |
(As an alternative, we could switch most tests to use port 0, and then check the logs for the OS-assigned port. But that's a lot more work.) |
Next Steps
Wait for this failure to happen again, so we can see the diagnostics we added in #1770.
Version
Zebra
main
, PR #1766, commit 79d45e7.Platform
Windows CI
Description
The
metrics_endpoint
test sometimes fails because the test can't connect to thezebrad
metrics listener.We don't know why, because the acceptance test doesn't show the
zebrad
logs for this error.Commands
zebrad start
with themetrics_endpoint
test config.Newer Logs
Older Logs
https://github.com/ZcashFoundation/zebra/pull/1766/checks?check_run_id=1919269780#step:8:1585
The text was updated successfully, but these errors were encountered: