Clustertest #1
Open
Clustertest #1
Conversation
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
The test suite + tests were written by Jan Wieck and Steve Singer. These tests are based on the clustertest framework
1. Ignore generated files (logs and such) 2. DB properties file is provided as a sample, so we aren't trying to overwrite, from the build, the user's version
- Add Java configuration file, with sample - Add more parms to DB properties file - Revisions to documentation based on all this - Mostly formatting changes to disorder tests
-Adding in E'' style character escaping to avoid warnings. -Changing some paths to included files to be correct
…. But seriously...]
This test was sometimes not finishing before the default WAIT FOR EVENT timeout
- test1 needs to wait for psql to finish before comparing the databases - Increase the standard time we wait for a slonik call to timeout. It was not long enough for some of the tests
Historically we refered to the shell versions of these tests as the regression tests. We will keep that name to distingiush them from the 'disorder' tests.
It was removed by a checkin pre the git migration. This table is used by the createSecondSet() function in BasicTests.js it is not used for a lot, but it is used.
…er test function which generated this bit of slonik code.
1. Make sure that we can adjust the frequency of the cleanup thread(broken today) 2. Make sure that events from origin nodes that have been deleted get removed from sl_log.
create set on a different node where a third node can see the drop set after the create set.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 have shifted configuration into ".sample" files, so that one may run tests out of a Git repo without getting pestered about issues surrounding merges into one's own custom configuration.
Added a shell script to wrap the Java, and revised the README to indicate all this.