-
Notifications
You must be signed in to change notification settings - Fork 594
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: deterministic e2e fuzz test returns broken hash_shuffle_channel
instead of ExprError::NumericOutOfRange
#7218
Comments
hash_shuffle_channel
instead of ExprError::NumericOutOfRange
hash_shuffle_channel
instead of ExprError::NumericOutOfRange
broken hash_shuffle_channel
instead of ExprError::NumericOutOfRange
Seems unable to reproduce so far. Will continue to monitor it. |
Seems related, although this issue was resolved. #4788 |
Resolved #7324 |
Actually because there are still some other bugs, I have revert this: #7455 (review) Can we tolerate the hash shuffle channel error in sqlsmith and mark it as a TODO temporarily? |
Sure, I think it's not urgent. Workaround for sqlsmith: It seldom happens, and usually goes away if re-run pipeline. |
Will tolerate hash shuffle channel error first |
Describe the bug
Deterministic e2e test fails due to broken channel error:
To Reproduce
Locally I have tried the query:
However it returns
Expr::OutOfRange
as expected. I'm not very sure why it returnsbroken hash_shuffle_channel
in CI instead.You may also try #7221 , to run it in ci. However I was unable to reproduce with this as well.
Expected behavior
It should return
Expr::OutOfRange
on deterministic fuzzing tests as well.Additional context
https://buildkite.com/risingwavelabs/main-cron/builds/296#01858474-6ab5-4b6d-b565-1feb9c8cf0be
The text was updated successfully, but these errors were encountered: