Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

IntegrityTest implementation should be feature gated #13094

Merged
merged 3 commits into from
Jan 11, 2023

Conversation

bkchr
Copy link
Member

@bkchr bkchr commented Jan 7, 2023

The initial implementation for the old declarative macros is still feature gating the implementation. As we only call this in a test, there is no need to have this compiled for wasm.

The initial implementation for the old declarative macros is still feature gating the
implementation. As we only call this in a test, there is no need to have this compiled for wasm.
@bkchr bkchr added A2-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. D3-trivial 🧸 PR contains trivial changes in a runtime directory that do not require an audit labels Jan 7, 2023
@@ -191,6 +191,7 @@ pub fn expand_hooks(def: &mut Def) -> proc_macro2::TokenStream {
}
}

#[cfg(feature = "std")]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Polkadot comp CI fails.
Looks like mock_msg_pallet does not have an std feature and therefore tries to compile the integrity tests without it.
In these cases we cannot run the integrity test, so the __construct_runtime_integrity_test should probably also be std-gated.
Or we fix the mock_msg_queue to have a std feature 🤷‍♂️

@bkchr bkchr requested a review from ggwpez January 11, 2023 14:43
@ggwpez
Copy link
Member

ggwpez commented Jan 11, 2023

bot merge

@paritytech-processbot paritytech-processbot bot merged commit e752af1 into master Jan 11, 2023
@paritytech-processbot paritytech-processbot bot deleted the bkchr-integrity-tests-std branch January 11, 2023 15:40
ltfschoen pushed a commit to ltfschoen/substrate that referenced this pull request Feb 22, 2023
)

* `IntegrityTest` implementation should be feature gated

The initial implementation for the old declarative macros is still feature gating the
implementation. As we only call this in a test, there is no need to have this compiled for wasm.

* Don't assume that all "consumers" have a `std` feature
ark0f pushed a commit to gear-tech/substrate that referenced this pull request Feb 27, 2023
)

* `IntegrityTest` implementation should be feature gated

The initial implementation for the old declarative macros is still feature gating the
implementation. As we only call this in a test, there is no need to have this compiled for wasm.

* Don't assume that all "consumers" have a `std` feature
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A2-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. D3-trivial 🧸 PR contains trivial changes in a runtime directory that do not require an audit
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants