Skip to content
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 unique non-zero exit code for failing tests #301

Merged
merged 2 commits into from
Feb 26, 2024
Merged

Conversation

Xenomega
Copy link
Member

This closes #289. It organizes exit code definitions into cmd/exitcodes/, adds a unique exit code for failed tests during a fuzz run, and adds a generic way to bubble up errors with exit codes from cmd to main.go.

Exit codes: 0 = success, 1 = general error, 7 = failed test.

Any future exit codes we add would be >7. I left a few as a gap since some errors (0-5) are more standard for other use cases on some platforms.

…e up errors with exit codes from cmd, organized exit code definitions into one package
@Xenomega Xenomega requested a review from anishnaik as a code owner February 20, 2024 20:03
@anishnaik anishnaik merged commit 729b78a into master Feb 26, 2024
9 checks passed
@anishnaik anishnaik deleted the dev/fuzz-exit-code branch February 26, 2024 20:11
Leeyah-123 pushed a commit to Leeyah-123/medusa that referenced this pull request Jun 4, 2024
…e up errors with exit codes from cmd, organized exit code definitions into one package (crytic#301)

Co-authored-by: anishnaik <[email protected]>
s4nsec pushed a commit that referenced this pull request Jul 9, 2024
…e up errors with exit codes from cmd, organized exit code definitions into one package (#301)

Co-authored-by: anishnaik <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

medusa fuzz exits with code 0 when an error is found
2 participants