You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is of interest, but I was tinkering with this today. It's a setup for generating random runs of operations in order to break MVStore. TestMVStoreFuzz.generateFuzzTests will generate random new runs and test them, keeping the ones which fail. TestMVStoreFuzz.replayTests will take the saved run files and and rerun them.
fuzz-0.txt org.h2.mvstore.MVStoreException: Chunk 1 not found [2.5.259/9] on a reopen
fuzz-1.txt: java.lang.StackOverflowError on a multiple version rollback
It's very possible some of these end up using MVStore incorrectly, in which case those tests could be discarded or maybe turned into more suitable error messages.
I use MVStore a lot in a couple of projects and experience some intermittent failures. I'm not smart enough to track down those failures nor fix them, but I can write code like this. Perhaps it can help make the library more resilient.
@kennethjor, Thank You for your contribution.
I've used you test and was able to reproduce failures, it uncovered. They all have the same root cause, and all are fixed now by #4386.
Was not able to find any more failures, so far.
As far as JUnit usage goes - decision was made long ago (right or wrong) to avoid it's use, so let's stick to that.
Once it's ready, please can you do a license statement to the google groups mailing list, as described at here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I don't know if this is of interest, but I was tinkering with this today. It's a setup for generating random runs of operations in order to break MVStore.
TestMVStoreFuzz.generateFuzzTestswill generate random new runs and test them, keeping the ones which fail.TestMVStoreFuzz.replayTestswill take the saved run files and and rerun them.fuzz-0.txtorg.h2.mvstore.MVStoreException: Chunk 1 not found [2.5.259/9] on a reopenfuzz-1.txt: java.lang.StackOverflowError on a multiple version rollbackIt's very possible some of these end up using MVStore incorrectly, in which case those tests could be discarded or maybe turned into more suitable error messages.
I use MVStore a lot in a couple of projects and experience some intermittent failures. I'm not smart enough to track down those failures nor fix them, but I can write code like this. Perhaps it can help make the library more resilient.