You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
axaysagathiya opened this issue
Jan 20, 2025
· 1 comment
Labels
A-debugissue requires detective debug work to figure out what's going wrong.S-runtimeissues related to the lib/runtime package.T-bugthis issue covers unexpected and/or wrong behaviour.
we don't get any error and still we get empty value.
Possible Solution
may be we need more test data. but what do we need?
To Reproduce
run TestInstance_ParachainHostClaimQueue unit test which is added in the PR: #4383.
Log output
> go test ./lib/runtime/wazero/... -v -run TestInstance_ParachainHostClaimQueue
=== RUN TestInstance_ParachainHostClaimQueue
=== PAUSE TestInstance_ParachainHostClaimQueue
=== CONT TestInstance_ParachainHostClaimQueue
2025-01-20T20:21:57+05:30 CRITICAL target=runtime::storage message=Corrupted state at `0x94eadf0156a8ad5156507773d0471e4a49f6c9aa90c04982c05388649310f22f`: Error ext_logging_log_version_1 pkg=runtime module=wazero
instance_test.go:1756:
Error Trace: /Users/axaysagathiya/code/github/gossamer/lib/runtime/wazero/instance_test.go:1756
Error: Should NOT be empty, but was map[]
Test: TestInstance_ParachainHostClaimQueue
--- FAIL: TestInstance_ParachainHostClaimQueue (3.55s)
FAIL
FAIL github.com/ChainSafe/gossamer/lib/runtime/wazero 4.246s
FAIL
The text was updated successfully, but these errors were encountered:
@axaysagathiya maybe you can try to use the runtime.WESTEND_RUNTIME_v1017001 for parachains host calls, since it was released Dec 17, 2024 and is the latest release
Just more info: Maybe the runtime you're using for testing does not have the correct on_chain_storage_version, which is 3 and maybe it is retrieving informations from the migration storage which is empty.
P1sar
added
the
A-debug
issue requires detective debug work to figure out what's going wrong.
label
Jan 23, 2025
A-debugissue requires detective debug work to figure out what's going wrong.S-runtimeissues related to the lib/runtime package.T-bugthis issue covers unexpected and/or wrong behaviour.
Bug summary
ParachainHostClaimQueue
runtime method in the PR: chore(candidate-backing): update active leaves #4383. but unit test fails for this methodExpected Behavior
Current Behavior
Possible Solution
To Reproduce
run
TestInstance_ParachainHostClaimQueue
unit test which is added in the PR: #4383.Log output
The text was updated successfully, but these errors were encountered: