Skip to content
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

zebra_zcash_listener_conflict test occasionally fails #3489

Closed
teor2345 opened this issue Feb 8, 2022 · 1 comment · Fixed by #3537
Closed

zebra_zcash_listener_conflict test occasionally fails #3489

teor2345 opened this issue Feb 8, 2022 · 1 comment · Fixed by #3537
Assignees
Labels
A-diagnostics Area: Diagnosing issues or monitoring performance A-network Area: Network protocol updates or fixes C-bug Category: This is a bug I-integration-fail Continuous integration fails, including build and test failures I-slow Problems with performance or responsiveness

Comments

@teor2345
Copy link
Contributor

teor2345 commented Feb 8, 2022

Motivation

The zebra_zcash_listener_conflict zebrad acceptance test occasionally fails with:

conflicted node2 was still running, but the test expected a panic

One of the launched processes does panic:

Message: Opening Zcash network protocol listener 127.0.0.1:58261 failed: Os { code: 98, kind: AddrInUse, message: "Address already in use" }. Hint: Check if another zebrad or zcashd process is running. Try changing the network listen_addr in the Zebra config.

The launch timing is right for node2, but the panic check isn't seeing the panic (it runs just before these lines):

    return node2
        .kill_on_error::<(), _>(Err(eyre!(

This has happened about once a day for the past week:
https://github.com/ZcashFoundation/zebra/runs/5114636264?check_suite_focus=true#step:13:1744

Diagnostic Suggestions

Turn on full backtraces in the acceptance tests using COLORBT_SHOW_HIDDEN=1.

Fix Suggestions

Use expect_stdout_line_matches right after node1 is launched, rather than using wait_with_output.
(node1 could be blocking on output, and never getting to run the conflicting port or file code.)

If this doesn't fix the bug, it will help with diagnostics.

Related Work

@ftm1000
Copy link

ftm1000 commented Feb 15, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Diagnosing issues or monitoring performance A-network Area: Network protocol updates or fixes C-bug Category: This is a bug I-integration-fail Continuous integration fails, including build and test failures I-slow Problems with performance or responsiveness
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants