Stream: git-wasmtime

Topic: wasmtime / issue #3935 Increase minimum instance threshol...

Wasmtime GitHub notifications bot (Mar 16 2022 at 16:36):

github-actions[bot] commented on issue #3935:

Subscribe to Label Action

cc @fitzgen

<details>
This issue or pull request has been labeled: "fuzzing"

Thus the following users have been cc'd because of the following labels:

• fitzgen: fuzzing

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

Wasmtime GitHub notifications bot (Mar 16 2022 at 18:18):

peterhuene commented on issue #3935:

Oh right! LGTM then.

Wasmtime GitHub notifications bot (Mar 16 2022 at 18:25):

alexcrichton commented on issue #3935:

Oh @peterhuene these limits are only used for the spectests fuzzer which simply runs all the *.wast spec tests in varying configurations of wasmtime, basically fuzzing that all our config permutations should all be able to run all the tests in the same way. In that sense we're not dealing with wasm-smith generated modules which might have 500 modules all have a linear memory that uses 900 pages, instead we're running specific tests which theoretically none of them should blow the 2GB limit.

Last updated: Nov 22 2024 at 16:03 UTC