cfallin opened PR #3844 from fuzz-epochs
to main
:
Without async fuzzing, we won't be able to test the most interesting
aspects of epoch interruption, namely the
interrupt/update-deadline/resume flow. However, the "trap on epoch
change" behavior works even for synchronous stores, and if we never
change the epoch, then we should see the same behavior as without epoch
interruption instrumentation.This will at least give us coverage of the codegen, and ensure that the
codegen is compatible with all control flow, etc. that we otherwise
generate; and will check one half of correct execution, namely "no
interruptions happen when we don't expect any".Created due to @alexcrichton noting that we don't have coverage of
epoch-related codegen in this oss-fuzz coverage report (thanks!).<!--
Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
cfallin requested alexcrichton for a review on PR #3844.
alexcrichton submitted PR review.
cfallin updated PR #3844 from fuzz-epochs
to main
.
alexcrichton submitted PR review.
cfallin merged PR #3844.
Last updated: Dec 23 2024 at 12:05 UTC