Skip to content
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

MultiChain part of standard Tribler unit test #1781

Closed
synctext opened this issue Dec 10, 2015 · 7 comments
Closed

MultiChain part of standard Tribler unit test #1781

synctext opened this issue Dec 10, 2015 · 7 comments
Assignees
Milestone

Comments

@synctext
Copy link
Member

complete scenario file for unit test

add existing scenario files to standard PR tester: https://jenkins.tribler.org/job/GH_Tribler_pull-request-tester_devel/
Existing written scenario, like: https://github.com/snorberhuis/gumby/blob/devel/experiments/multichain/multichain_integrated_single.scenario
Ensure that the scenario files do not overload the test machine.
Create a screenshot of the results: image

After integration: check counters and fix

@whirm
Copy link

whirm commented Dec 11, 2015

@synctext Just to clarify, you are talking about running the experiment in parallel with the tests, right?

@synctext
Copy link
Member Author

yes.
Could be nice part of the standard test suite, if rock solid stable.

@whirm
Copy link

whirm commented Dec 11, 2015

If it's using scenario files it's using gumby, it would be neither trivial or a good idea to have tests depending on that. What I think we should have is a comparative experiment execution system added to gumby.

Similar to the performance regression analysis paper but way simpler (no systemtap involved, just some basic metrics comparison against the results from the target branch).

All this experiments could be run in parallel with the unit tests and the results reported on each PR. If the changes make any of them worse than the current code, it fails the build.

This should be pretty easy to implement and we could even use @corpaul's already existing code.

But for starters, I would just create a new job that gets triggered with each PR, this way we get a link to the resulting report just like with the tests and then we can keep improving it.

@synctext synctext added this to the Sprint 2 milestone Jan 5, 2016
@synctext
Copy link
Member Author

synctext commented Jan 5, 2016

Good point. Lets keep it as simple as possible for now. A new job with this picture as output.
No performance regression yet. That is where we want to end up later. Just a picture using .gv format generated using cmdline tools, like we did 7 years ago.
http://kayapo.tribler.org/trac/raw-attachment/wiki/SwarmBasedReputationConsensus/bartercast_graph_all_records_till_0806.gv

@pimveldhuisen
Copy link
Member

First image:
https://jenkins.tribler.org/job/MultiChain_integrated_experiment_pim/43/
This could be refined some more of course.

@pimveldhuisen
Copy link
Member

The experiment now renders svg images with colored nodes:
https://jenkins.tribler.org/job/MultiChain_integrated_experiment_pim/61/
Green nodes are origin nodes (light green: origin for both peers, dark green: origin for one of the peers).
Red nodes are half signed nodes.
Is this sufficient to close this issue?

@synctext
Copy link
Member Author

image
Yes, Looks good; feel free to close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants