-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachtest: sqlsmith/setup=rand-tables/setting=no-ddl failed #66708
Comments
This looks similar to #66306. It seems like a similar issue may still be lurking somewhere.... Confirmed that I can reproduce by running the output of the sqlsmith.log from the test artifacts |
|
roachtest.sqlsmith/setup=rand-tables/setting=no-ddl failed with artifacts on master @ 95028269160e0bfa2b94477238e72670bf780e9d:
Reproduce
To reproduce, try: # From https://go.crdb.dev/p/roachstress, perhaps edited lightly.
caffeinate ./roachstress.sh sqlsmith/setup=rand-tables/setting=no-ddl |
reduction sql:
|
Tiny bit simpler:
This did not hit the panic:
|
Nice, thanks @michae2 ! |
66845: storage: add Reader method to pin iterators at current engine state r=sumeerbhola a=sumeerbhola This is relevant for read evaluation cases where we want to release latches before evaluation. The new Reader.PinEngineStateForIterators method would be called before releasing latches. This pinning does not apply to iterators with timestamp hints, similar to how ConsistentIterators does not apply to them. So this does not help ExportRequest evaluation for incremental backups. To address this we would want a guarantee from the caller that the timestamp hints will not change for the lifetime of the Reader that is making a promise of ConsistentIterators. Informs #55461,#66485 Release note: None 66885: sql: add ReType to resolveAndRequireType to fix vector engine panic r=cucaroach a=cucaroach Fixes #66708 The vector engine needs exact type coercion, specifically when piping computed column values into downstream operators. Without this fix the computed column was left as an int64 instead of cast back to the required int16 type. Exposed by sqlsmith, kudos to @michae2 for the reduce help Release note: None Co-authored-by: sumeerbhola <[email protected]> Co-authored-by: Tommy Reilly <[email protected]>
Fixes cockroachdb#66708 The vector engine needs exact type coercion, specifically when piping computed column values into downstream operators. Without this fix the computed column was left as an int64 instead of cast back to the required int16 type. Exposed by sqlsmith, kudos to @michae2 for the review help Release note: None
Fixes cockroachdb#66708 The vector engine needs exact type coercion, specifically when piping computed column values into downstream operators. Without this fix the computed column was left as an int64 instead of cast back to the required int16 type. Exposed by sqlsmith, kudos to @michae2 for the review help Release note: None
Since this came from sqlsmith and has not been seen in the wild and we aren't sure about the ramifications of the extra casting this change introduces @RaduBerinde thinks we don't need to backport this, at least not as is. |
roachtest.sqlsmith/setup=rand-tables/setting=no-ddl failed with artifacts on master @ 19865dd4d29e87212f36b237aaaf543a7d9d55f5:
Reproduce
To reproduce, try:
# From https://go.crdb.dev/p/roachstress, perhaps edited lightly. caffeinate ./roachstress.sh sqlsmith/setup=rand-tables/setting=no-ddl
This test on roachdash | Improve this report!
The text was updated successfully, but these errors were encountered: