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.

Sign up for GitHub

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

Jump to bottom

tests(fuzz): Add parse_date fuzzing target #1127

Merged
merged 1 commit into from
Aug 17, 2024
Merged

tests(fuzz): Add parse_date fuzzing target #1127

merged 1 commit into from
Aug 17, 2024

Conversation

caspermeijn
Copy link
Collaborator

Add a fuzzing target for parsing into a Timestamp and comparing the result with crate chrono.

@caspermeijn
tests(fuzz): Add parse_date fuzzing target
2c34a40 
Add a fuzzing target for parsing into a Timestamp and comparing the result with crate chrono.
@caspermeijn
Copy link
Collaborator Author

@mumbleskates This is the fuzzer I used for my testing. Do you have suggestions?

mumbleskates
mumbleskates approved these changes Aug 16, 2024
View reviewed changes
Copy link
Contributor

@mumbleskates mumbleskates left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks good! when i tried to do it the first time i think i called the wrong chrono parsing function or something and it was accepting years with too few digits so i had a lot of annoying problems with that, but this is very nice.

@caspermeijn caspermeijn added this pull request to the merge queue Aug 17, 2024
Merged via the queue into tokio-rs:master with commit df3e58e Aug 17, 2024
16 checks passed
@caspermeijn caspermeijn deleted the fuzz_date_time branch August 17, 2024 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mumbleskates mumbleskates mumbleskates approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@caspermeijn @mumbleskates