remlse opened PR #6254 from remlse:fuzz-randomize-block-order
to bytecodealliance:main
:
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->relates to #4134
The block lowering order should have no impact on correctness, so we may randomize it during fuzzing.
remlse updated PR #6254.
remlse updated PR #6254.
remlse updated PR #6254.
remlse updated PR #6254.
remlse updated PR #6254.
remlse updated PR #6254.
remlse has marked PR #6254 as ready for review.
remlse requested jameysharp for a review on PR #6254.
remlse requested wasmtime-compiler-reviewers for a review on PR #6254.
remlse requested wasmtime-default-reviewers for a review on PR #6254.
cfallin submitted PR review:
This looks great -- thanks!
Just one potential optimization below, then happy to merge.
cfallin submitted PR review:
This looks great -- thanks!
Just one potential optimization below, then happy to merge.
cfallin created PR review comment:
s/shoud/should/
Also let's reword this slightly to something like "If chaos-mode is enabled in the control plane, arbitrarily reorder ..." just to emphasize that
shuffle
is a no-op in the common (normal/release build) case.
cfallin created PR review comment:
Can we add an early-out conditional to
shuffle
along the lines of what this comment describes (if data is exhausted ...)? The effect is the same now but we construct anUnstructured
, take a slice, and do some other work before we hit thebreak
with the current code.
remlse updated PR #6254.
cfallin has enabled auto merge for PR #6254.
remlse updated PR #6254.
remlse updated PR #6254.
cfallin has enabled auto merge for PR #6254.
remlse updated PR #6254.
cfallin submitted PR review:
LGTM on latest with naming nit, thanks!
Out of curiosity, have you fuzzed with this (and verified that no issues arise)?
cfallin submitted PR review:
LGTM on latest with naming nit, thanks!
Out of curiosity, have you fuzzed with this (and verified that no issues arise)?
cfallin created PR review comment:
Let's call this
shuffled(iter)
or similar, perhaps? Otherwise we're using two different technical words ("shuffle" and "permutation") for method names, which seems unnecessary to me.
remlse updated PR #6254.
cfallin merged PR #6254.
Last updated: Nov 22 2024 at 17:03 UTC