-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Validation: don't detect STDIN closing when running in process #1695
Validation: don't detect STDIN closing when running in process #1695
Conversation
It should not matter. The validation subprocess is spawned with I failed to spot when reviewing #1622 how |
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.
Yeah, I see it as @arkpar and I already told you this in Element. The thread does not even care about stdin.
runtime/westend/src/lib.rs
Outdated
@@ -84,7 +84,7 @@ pub const VERSION: RuntimeVersion = RuntimeVersion { | |||
spec_name: create_runtime_str!("westend"), | |||
impl_name: create_runtime_str!("parity-westend"), | |||
authoring_version: 2, | |||
spec_version: 43, | |||
spec_version: 44, |
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.
Revert please
7a7dca9
to
66a8654
Compare
OK!! I get it now. Sorry I missed completely the point in the previous PR. I just pushed something that is more like you said. This is what you had in mind? (but with the pool in the enum would be better XD) (quick response would be appreciated) cc @arkpar |
parachain/src/wasm_executor/mod.rs
Outdated
@@ -166,7 +184,7 @@ pub fn validate_candidate_internal( | |||
) -> Result<ValidationResult, ValidationError> { | |||
let executor = sc_executor::WasmExecutor::new( | |||
#[cfg(not(any(target_os = "android", target_os = "unknown")))] | |||
sc_executor::WasmExecutionMethod::Compiled, | |||
sc_executor::WasmExecutionMethod::Interpreted, |
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.
may I ask why it was changed?
not sure how much of that code will be retained given #1609
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.
I had compilation issue. Will revert it to see
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.
In the previous backport I had to remove the feature wasmtime because the CI failed like this: https://gitlab.parity.io/parity/polkadot/-/jobs/635768
And now it's failing because of:
error[E0599]: no variant or associated item named `Compiled` found for enum `WasmExecutionMethod` in the current scope
--> parachain/src/wasm_executor/mod.rs:187:37
|
187 | sc_executor::WasmExecutionMethod::Compiled,
| ^^^^^^^^ variant or associated item not found in `WasmExecutionMethod`
error: aborting due to previous error
For more information about this error, try `rustc --explain E0599`.
error: could not compile `polkadot-parachain`.
So I talked to @bkchr and apparently I can ignore the failing test for now
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
* master: Companion PR for #6984 (#1661) Update some dependencies. (#1718) Add a specific memory requirements (#1716) Companion PR for #7039: grandpa-rpc dont share subscription manager, only executor (#1687) Update bytes. (#1715) Add a note about memory requirements (#1714) Update parity-multiaddr. (#1700) typo in proxy tests (#1713) Companion PR for ` Add a `build-sync-spec` subcommand and remove the CHT roots from the light sync state.` (#1670) Forwardport: Validation: don't detect STDIN closing when running in process (#1695) (#1703)
I had an issue in paritytech/cumulus#201 because the test was working locally but not on CI and I couldn't figure out why. I finally found out why: when running in a CI, the STDIN is actually closed. Because of that, the exit detection mechanism was triggered and the validation was never run.
This PR proposes to fix this by adding a flag that activates this exit mechanism. So when the validation is ran "in process", it will disable the flag and let the validation run indefinitely.
Related to #1622