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

Retire puppet workers #583

Closed
s0me0ne-unkn0wn opened this issue Aug 8, 2023 · 1 comment · Fixed by #1449
Closed

Retire puppet workers #583

s0me0ne-unkn0wn opened this issue Aug 8, 2023 · 1 comment · Fixed by #1449

Comments

@s0me0ne-unkn0wn
Copy link
Contributor

After worker separation and liberation, puppet workers used for integration tests will not be needed anymore. Their additional functionality (that is only used for those tests) may be integrated into the real workers and gated through #[cfg(test)], as discussed here.

Also, it'd probably open the way for the refactoring of real workers which may be placed into corresponding binary crates in node/core/pvf without the necessity to have separate library and binary crates for every of them.

@mrcnski
Copy link
Contributor

mrcnski commented Aug 8, 2023

Their additional functionality (that is only used for those tests) may be integrated into the real workers and gated through #[cfg(test)]

Good idea, just keep in mind that #[cfg(test)] may not work across crates. (Maybe can instead use the new test-utils feature.)

@Sophia-Gold Sophia-Gold transferred this issue from paritytech/polkadot Aug 24, 2023
s0me0ne-unkn0wn added a commit that referenced this issue Sep 11, 2023
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.
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
* fix grandpa initialization

* fnt
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
* fix grandpa initialization

* fnt
bkchr pushed a commit that referenced this issue Apr 10, 2024
* fix grandpa initialization

* fnt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants