Skip to content

Verify how wasmd reacts when gas runs out during execution #8

Closed
@ethanfrey

Description

@ethanfrey

Summary

We should test two cases:

  • infinite loop in wasm, that runs out of gas in cpu cycles
  • loop on kvstore access, gas runs out when calling into go KVStore code

Problem Definition

In both cases, the tx should return an error, and not panic the wasmd process.

We also should ensure the cosmwasm-vm is not left in an invalid state. You can test this by calling a second tx to the same contract - ideally one that shouldn't fail. If we leave an invalid contract state inside the LRU cache, we will have problems, otherwise there should be no influence between consequtive runs.

Proposal


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions