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

chore(dot/parachain): consistently use ParaID type #4273

Merged
merged 2 commits into from
Oct 30, 2024

Conversation

haikoschol
Copy link
Contributor

Changes

No functional changes, just mechanically replacing uint32 with parachaintypes.ParaID.

Tests

go test ./...

Issues

Closes #3883

@haikoschol haikoschol enabled auto-merge (squash) October 28, 2024 11:54
@axaysagathiya
Copy link
Contributor

axaysagathiya commented Oct 29, 2024

TestCandidateValidation_processMessageValidateFromChainState test fails because of Unexpected call to *candidatevalidation.MockInstance.ParachainHostPersistedValidationData.

We will have to modify the test to include the mock instance as one of the test-case fields. Each test case will have its own mock instance, so we can run all test cases in parallel.

Some changes to parachaintypes.ParaID were missing in mocked calls,
which let to the tests not terminating in GitHub Actions.

The fix slightly changes the semantics of the tests in
TestCandidateValidation_processMessageValidateFromChainState. Before,
one candidate validation subsystem was created and used for all
subtests. Now one is created for each subtest.
@haikoschol haikoschol merged commit eea08cb into feat/parachain Oct 30, 2024
22 checks passed
@haikoschol haikoschol deleted the haiko/para-id branch October 30, 2024 10:31
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 this pull request may close these issues.

5 participants