-
Notifications
You must be signed in to change notification settings - Fork 8
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
Architecture to add libp2p tests #198
Comments
Working on this today. |
@vasco-santos I've added a branch with a design diagram. |
@vasco-santos I've made a design diagram The main difference is the |
Thanks for the proposal @Elexy ! So, in this approach we need to use this repo for all the tests and mark each test as being part of a project? |
Hi @vasco-santos We could generalize is even more and make it a generic runner, able to run arbitrary scripts and retrieve the output, but I'd say we'd probably be building a full blow CI system. |
I understand that generalize this solution more, at least at this moment seems not the best approach. I would like to have the |
@vasco-santos that makes sense. |
@Elexy I think the js-ipfs tests in the repo are fine, he just wants to pull another repo that will need to be synced by the runner. @vasco-santos did I read that right? |
Yes, we should be able to get tests from other repos, such as |
Currently we are |
As discussed in the latest sync call I want to present a proposal to allow the runner to run benchmark tests from a different repository. |
Thanks for the proposal @Elexy ! |
Question that came out is they want to write benchmarks against libp2p. We can clone the repo and infrastructure for libp2p or add the login in the runner to use the libp2p or js-ipfs repo. The same dashboard could be used and filter by project.
@e_lexy @Matteo ^^^^^ when you get a chance thoughts on the above.
matteo [5:12 PM]
@e_lexy you do the architecture for that solution? Sharing things might be good.. up to deploying a double.
What’d be the cleanest way?
Can you assemble a proposal on an gdoc and I’ll review?
The text was updated successfully, but these errors were encountered: