-
Notifications
You must be signed in to change notification settings - Fork 689
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
Retire puppet workers #1449
Retire puppet workers #1449
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really happy to see this!
This requires the workers to be built before running tests, right? Instructions should be added to the relevant READMEs, like we do for polkadot-test-service
.
@mrcnski I've added a README to the PVF host integration tests directory. Not sure if it has to be added somewhere else, all the other tests seem good to go, but I may be missing something. |
let mut workers_path = std::env::current_exe().unwrap(); | ||
workers_path.pop(); | ||
workers_path.pop(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add this bit of logic to a helper function? it's being used from multiple places
Closes #583
After the separation of PVF worker binaries, dedicated puppet workers are not needed for tests anymore. The production workers can be used instead, avoiding some code duplication and decreasing complexity.
The changes also make it possible to further refactor the code to isolate workers completely.