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

[Bug]: test_unary_propose_fast_path_fallback_slow_path will randomly failed #840

Closed
1 task done
Phoenix500526 opened this issue Jun 7, 2024 · 2 comments · Fixed by #859
Closed
1 task done

[Bug]: test_unary_propose_fast_path_fallback_slow_path will randomly failed #840

Phoenix500526 opened this issue Jun 7, 2024 · 2 comments · Fixed by #859
Assignees
Labels
bug Something isn't working

Comments

@Phoenix500526
Copy link
Collaborator

Description about the bug

As the title described, the test case test_unary_propose_fast_path_fallback_slow_path will randomly failed.

Version

0.6.1 (Default)

Relevant log output

--- STDOUT:              curp client::tests::test_unary_propose_fast_path_fallback_slow_path ---

running 1 test
2024-06-07T07:51:50.826655Z  WARN test_unary_propose_fast_path_fallback_slow_path: curp::client::unary: propose cmd(0#16819838916010368377) to server(4) error: KeyConflict(())
2024-06-07T07:51:50.826753Z  WARN test_unary_propose_fast_path_fallback_slow_path: curp::client::unary: propose cmd(0#16819838916010368377) to server(3) error: KeyConflict(())
2024-06-07T07:51:50.927001Z DEBUG test_unary_propose_fast_path_fallback_slow_path: curp::client::unary: slow round for cmd(0#16819838916010368377) succeed
test client::tests::test_unary_propose_fast_path_fallback_slow_path ... FAILED

failures:

failures:
    client::tests::test_unary_propose_fast_path_fallback_slow_path

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 112 filtered out; finished in 0.11s


--- STDERR:              curp client::tests::test_unary_propose_fast_path_fallback_slow_path ---
thread 'client::tests::test_unary_propose_fast_path_fallback_slow_path' panicked at crates/curp/src/client/tests.rs:583:5:
assertion `left == right` failed
  left: 3
 right: 5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

   Canceling due to test failure: 3 tests still running
        PASS [   0.023s] curp client::tests::test_unary_slow_round_fetch_leader_first
        PASS [   0.123s] curp client::tests::test_unary_propose_slow_path_works
        PASS [   1.910s] benchmark bench_client::test::test_new_etcd_client
        PASS [   2.092s] benchmark bench_client::test::test_new_xline_client
------------
     Summary [   2.101s] 25/345 tests run: 24 passed, 1 failed, 0 skipped
        FAIL [   0.125s] curp client::tests::test_unary_propose_fast_path_fallback_slow_path
error: test run failed
error: process didn't exit successfully: `/github/home/.rustup/toolchains/1.74.0-x86_64-unknown-linux-gnu/bin/cargo nextest run --manifest-path /__w/Xline/Xline/Cargo.toml --target-dir /__w/Xline/Xline/target/llvm-cov-target --all-features --workspace` (exit status: 100)
Error: Process completed with exit code 1.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Phoenix500526 Phoenix500526 added the bug Something isn't working label Jun 7, 2024
Copy link

github-actions bot commented Jun 7, 2024

👋 Thanks for opening this issue!

Reply with the following command on its own line to get help or engage:

  • /contributing-agreement : to print Contributing Agreements.
  • /assignme : to assign this issue to you.

@CrystalAnalyst
Copy link
Contributor

This reason is located and solved in PR : #859

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants