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
For agoric-upgrade-10, the bootstrap ava tests were good for reasonably fast iteration with the benefit of debugger access. But as we revise components such as zoe, they bootstrap with the new code. But what we need to do is test the revised components in the context of a chain that bootstrapped from the earlier code.
Description of the Design
options include:
start an agoric-upgrade-10 like chain (using the docker upgrade-test framework, for example) and capture the kernel DB for use as a test fixture. Where we currently use makeSwingsetTestKit to initialize swingset, instead continue from the fixture DB.
bundle the agoric-upgrade-10 components as test fixtures and use them to initialize the swingset
#7969 is my current work-around. It's a test that will run at top-of-tree before the changes, and upgrade to bundles that were produced in a PR that includes the changes (#7966). I don't expect to check 7969 in, it's just there to give my reviewers confidence that the changes would work if installed. The scripts in 7966 and 7969 could probably be used in the upgrade-test framework.
splicing a bundle for zoe into the bootstrap is one thing, cuz it's in the swingset config file bundles section. But the vaultFactory and auction contracts come in by way of coreProposals. @michaelfig any clues?
I explored the idea of resuming from a swingset DB... it might work if we're OK with XS workers. But node workers are pretty valuable for debugging. Is there a way to ignore the difference during replay? @mhofman ? @FUDCo
Is there a way to ignore the difference during replay?
Can you clarify what you mean? Are you trying to replay XS worker transcripts in a node worker? I don't know if we'd be able to support that given the major GC differences.
What is the Problem Being Solved?
For
agoric-upgrade-10
, the bootstrap ava tests were good for reasonably fast iteration with the benefit of debugger access. But as we revise components such as zoe, they bootstrap with the new code. But what we need to do is test the revised components in the context of a chain that bootstrapped from the earlier code.Description of the Design
options include:
agoric-upgrade-10
like chain (using the docker upgrade-test framework, for example) and capture the kernel DB for use as a test fixture. Where we currently usemakeSwingsetTestKit
to initialize swingset, instead continue from the fixture DB.agoric-upgrade-10
components as test fixtures and use them to initialize the swingsetSecurity / Scaling Considerations
none?
Test Plan
This is all about designing a test plan.
cc @turadg @Chris-Hibbert
The text was updated successfully, but these errors were encountered: