-
Notifications
You must be signed in to change notification settings - Fork 65
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
crash_test: failures are reported when running with the new memtable #98
Comments
The test seems to fail for now, so in order to avoid headaches for devs working on `main`, let's not test the new memtable until the issues are fixed. This is not intended as a fix for #98, but rather as a temporary workaround to allow testing to continue, since no one is supposed to be using the new memtable yet.
The test seems to fail for now, so in order to avoid headaches for devs working on `main`, let's not test the new memtable until the issues are fixed. This is not intended as a fix for #98, but rather as a temporary workaround to allow testing to continue, since no one is supposed to be using the new memtable yet.
@hilikspdb please review 22-spdb-memtable |
PR #142 |
Stress tests failed: |
QAblackbox, whitebox, asan blackbox, db fuzzer and db map fuzzer all passed on: |
The test seems to fail for now, so in order to avoid headaches for devs working on `main`, let's not test the new memtable until the issues are fixed. This is not intended as a fix for #98, but rather as a temporary workaround to allow testing to continue, since no one is supposed to be using the new memtable yet.
QA passed on 20a75d1 22-spdb-memtable-blueberry |
QA passed on 03b830d |
Switch functionality #14 was added this ticket |
Import shorten memtable switch latency (#14)
Import shorten memtable switch latency (#14)
Import shorten memtable switch latency (#14)
Import shorten memtable switch latency (#14)
The test seems to fail for now, so in order to avoid headaches for devs working on `main`, let's not test the new memtable until the issues are fixed. This is not intended as a fix for #98, but rather as a temporary workaround to allow testing to continue, since no one is supposed to be using the new memtable yet.
The test seems to fail for now, so in order to avoid headaches for devs working on `main`, let's not test the new memtable until the issues are fixed. This is not intended as a fix for #98, but rather as a temporary workaround to allow testing to continue, since no one is supposed to be using the new memtable yet.
Import shorten memtable switch latency (#14)
The test seems to fail for now, so in order to avoid headaches for devs working on `main`, let's not test the new memtable until the issues are fixed. This is not intended as a fix for #98, but rather as a temporary workaround to allow testing to continue, since no one is supposed to be using the new memtable yet.
Import shorten memtable switch latency (#14)
Import shorten memtable switch latency (#14)
The test seems to fail for now, so in order to avoid headaches for devs working on `main`, let's not test the new memtable until the issues are fixed. This is not intended as a fix for #98, but rather as a temporary workaround to allow testing to continue, since no one is supposed to be using the new memtable yet.
Import shorten memtable switch latency (#14)
Import shorten memtable switch latency (#14)
The test seems to fail for now, so in order to avoid headaches for devs working on `main`, let's not test the new memtable until the issues are fixed. This is not intended as a fix for #98, but rather as a temporary workaround to allow testing to continue, since no one is supposed to be using the new memtable yet.
Import shorten memtable switch latency (#14)
When running the crash tests, all of them fail quickly with:
as well as
and
(all of the examples are taken from here).
This is happening only when running with the new memtable, which was merged as part of #22, and enabled in crash tests with #89 + #93.
To Reproduce
make crash_test
Expected behavior
Crash test succeeds.
System
Additional context
N/A
The text was updated successfully, but these errors were encountered: