Skip to content

test_esplora_sync is flaky #2032

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

Closed
TheBlueMatt opened this issue Feb 14, 2023 · 2 comments · Fixed by #2033
Closed

test_esplora_sync is flaky #2032

TheBlueMatt opened this issue Feb 14, 2023 · 2 comments · Fixed by #2033
Assignees
Milestone

Comments

@TheBlueMatt
Copy link
Collaborator

CI said this on an unrelated PR:

running 1 test
test test_esplora_syncs ... FAILED

failures:
error: test failed, to rerun pass `--test integration_tests`

---- test_esplora_syncs stdout ----
thread 'test_esplora_syncs' panicked at 'called `Result::unwrap()` on an `Err` value: JSON(Error("expected value", line: 1, column: 1))', lightning-transaction-sync/tests/integration_tests.rs:63:70
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    test_esplora_syncs

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.55s
@tnull
Copy link
Contributor

tnull commented Feb 15, 2023

Ugh, this is weird. I'll put some changes up that should make it more robust by giving the bitcoind/electrsd instances more leeway.

@TheBlueMatt
Copy link
Collaborator Author

No rush, its probably just CI being garbage and impossibly slow, as usual.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants