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: panicked at barrier/schedule.rs:244:18 #15848

Closed
fuyufjh opened this issue Mar 21, 2024 · 1 comment · Fixed by #15851
Closed

bug: panicked at barrier/schedule.rs:244:18 #15848

fuyufjh opened this issue Mar 21, 2024 · 1 comment · Fixed by #15851
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@fuyufjh
Copy link
Member

fuyufjh commented Mar 21, 2024

Describe the bug

Failure in recovery test: https://buildkite.com/risingwavelabs/main-cron/builds/2104#018e5c98-0655-4b21-b3d1-343a8b3bf96c/99

Error message/log

thread '<unnamed>' panicked at /risingwave/src/meta/src/barrier/schedule.rs:244:18:
called `Result::unwrap()` on an `Err` value: RecvError(())
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
             at ./src/meta/src/barrier/schedule.rs:244:9
             at ./src/meta/src/barrier/schedule.rs:327:59
             at ./src/meta/service/src/stream_service.rs:72:69
             at ./src/prost/src/sim/meta.rs:2980:30
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
context: node=6 "meta-3", task=731805 (spawned at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/madsim-tonic-0.4.1+0.10.0/src/transport/server.rs:275:13)
note: run with `MADSIM_TEST_SEED=10` environment variable to reproduce this error

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

@fuyufjh fuyufjh added the type/bug Something isn't working label Mar 21, 2024
@github-actions github-actions bot added this to the release-1.8 milestone Mar 21, 2024
@fuyufjh
Copy link
Member Author

fuyufjh commented Mar 21, 2024

Suspect it might be related to #13108

cc. @yezizp2012 Can you please take a look?

@fuyufjh fuyufjh changed the title bug: panicked at /risingwave/src/meta/src/barrier/schedule.rs:244:18: bug: panicked at barrier/schedule.rs:244:18 Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants