Currently Execute.tiering is a global flag referenced by all instances of Wasm stacks and the runtime. This makes extending ExeTester difficult as Execute.tiering can be set in arbitrary order when running the tests (its constructor sets Execute.tiering). I think we should look into refactoring away this global state.
Currently
Execute.tieringis a global flag referenced by all instances of Wasm stacks and the runtime. This makes extendingExeTesterdifficult asExecute.tieringcan be set in arbitrary order when running the tests (its constructor setsExecute.tiering). I think we should look into refactoring away this global state.