New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Reproducible Error Injection [3.0] #21720
Open
bernd-edlinger
wants to merge
4
commits into
openssl:openssl-3.0
Choose a base branch
from
bernd-edlinger:add_error_injection_30
base: openssl-3.0
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add Reproducible Error Injection [3.0] #21720
bernd-edlinger
wants to merge
4
commits into
openssl:openssl-3.0
from
bernd-edlinger:add_error_injection_30
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds reproducible memory error and test-data error injection, to the fuzzy-test framework. This feature can be enabled with ./config -DERROR_INJECT and additionally to enable call stacks -DERROR_CALLSTACK If enable-asan is used, the callstack is printed by the sanitizer, otherwise please set a breakpoint at the function "break_here", which is executed each time a memory allocation error is injected. If called with the environment variable ERROR_INJECT defined to the empty string the initialization value is printed, and can be used to reproduce the failure later, by passing the value to the ERROR_INJECT variable. There is a search script that can be used to look for errors, and print the command to reproduce the bug: ./testrun.sh This runs in endless mode until an error is found.
There is already one Error Detected here: https://github.com/openssl/openssl/actions/runs/5829582130
|
The latest CI test run https://github.com/openssl/openssl/actions/runs/5902344013
|
t8m
added
triaged: bug
The issue/pr is/fixes a bug
tests: present
The PR has suitable tests present
labels
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
branch: 3.0
Merge to openssl-3.0 branch
tests: present
The PR has suitable tests present
triaged: bug
The issue/pr is/fixes a bug
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds reproducible memory error and test-data
error injection, to the fuzzy-test framework.
This feature can be enabled with ./config -DERROR_INJECT and additionally to enable call stacks -DERROR_CALLSTACK
If enable-asan is used, the callstack is printed by the sanitizer, otherwise please set a breakpoint
at the function "break_here", which is executed each time a memory allocation error is injected.
If called with the environment variable ERROR_INJECT defined to the empty string the initialization value is printed, and can be used to reproduce the failure later, by passing the value to the ERROR_INJECT variable.
There is a search script that can be used to look
for errors, and print the command to reproduce the bug:
./testrun.sh
This runs in endless mode until an error is found.
Checklist