Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
W
wendelin.core
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Labels
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Commits
Open sidebar
Kirill Smelkov
wendelin.core
Commits
aa39eff1
Commit
aa39eff1
authored
Jun 05, 2020
by
Kirill Smelkov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
.
parent
9f60147d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
5 deletions
+8
-5
wcfs/testprog/treegen.py
wcfs/testprog/treegen.py
+8
-5
No files found.
wcfs/testprog/treegen.py
View file @
aa39eff1
...
...
@@ -44,7 +44,8 @@ Tree states are specified on stdin as topology-encoded strings, 1 state per 1 li
For every request the tree is changed and modifications are committed to database.
For every made commit corresponding transaction ID is printed to stdout.
The tree, that `treegen trees` works on, is also accessible via zconn.root()['treegen/tree'].
The tree, that `treegen trees` generates and works on, is also accessible via
zconn.root()['treegen/tree'].
Trees protocol specification:
...
...
@@ -71,10 +72,12 @@ allstructs
`treegen allstructs` generates topologies for subset of all possible tree
changes in between two trees specified by two key->value dicts.
For every kv the following tree topologies are used: 1) native (the one that
ZODB would usually create natively via regular usage), and 2) n random ones.
Then tree topologies are emitted corresponding to tree1->tree2 and tree1<-tree2
transitions for all combinations of (tree1, tree2) pairs.
For every kv the following tree topologies are considered: 1) native (the one
that ZODB would usually create natively via regular usage), and 2) n random
ones. Then tree topologies are emitted corresponding to tree1->tree2 and
tree1<-tree2 transitions for all combinations of (tree1, tree2) pairs.
The output of `treegen allstructs` is valid input for `treegen trees`.
Allstructs protocol specification:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment