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

Coretime Zombienet Test #2310

Closed
2 of 7 tasks
eskimor opened this issue Nov 14, 2023 · 3 comments
Closed
2 of 7 tasks

Coretime Zombienet Test #2310

eskimor opened this issue Nov 14, 2023 · 3 comments
Assignees

Comments

@eskimor
Copy link
Member

eskimor commented Nov 14, 2023

Setup a Zombienet with coretime parachain and make it send an assignment over to the relay chain. See it getting served. (Second parachain)

Network must be bootstrapped - coretime chain must have a core on the relay chain pre-configured.

Tasks

  • Fix Westend (migrations)
  • Fix Rococo - remove WeightInfo
  • Make CI pass
  • Add dummy WeightInfo for exposed assign_core call
  • Add configurations:
    • No legacy cores
    • Two bulk cores: one idling, one for coretime itself (pre-assigned) (currently we recycled the on_demand_cores config - so set this to 2, to get 2 core time cores)

Then have Coretime chain assign another para to the unoccupied core and see the other parachain starting to produce blocks: Tada! First basic test passed and we go from there.

Later Phase

Next up, would likely be core time chain actually manipulating the core count, after we implemented request_core_count.

If we move system chains over, we should test that this works smoothly. Core number will likely change, which should not matter, but worth testing.

@eskimor
Copy link
Member Author

eskimor commented Nov 16, 2023

We need to provide matching initial configurations for relay chain and core time chain.

@kamilsa
Copy link

kamilsa commented Jan 10, 2024

@eskimor am I right that there no available coretime zombienet tests? We were curious to run them with Kagome

@bkchr
Copy link
Member

bkchr commented Jan 10, 2024

There is one: #2867

I think we can also close this ticket now.

@bkchr bkchr closed this as completed Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Completed
Development

No branches or pull requests

4 participants