-
Notifications
You must be signed in to change notification settings - Fork 450
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
Comments
@synctext Just to clarify, you are talking about running the experiment in parallel with the tests, right? |
yes. |
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. |
Good point. Lets keep it as simple as possible for now. A new job with this picture as output. |
First image: |
The experiment now renders svg images with colored nodes: |
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:
After integration: check counters and fix
The text was updated successfully, but these errors were encountered: