-
Notifications
You must be signed in to change notification settings - Fork 71
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
Revive the fuzz testing framework #429
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!!
Could it be possible to add a very short fuzzing run (maybe only building?) to the per-PR CI so that we are sure that it still works overtime?
fuzz/Cargo.toml
Outdated
@@ -20,7 +20,7 @@ lazy_static = "1.4.0" | |||
arbitrary = { version = "0.4.0", features = ["derive"] } | |||
|
|||
[build-dependencies] | |||
parsec-client = "0.4.0" | |||
parsec-client = "0.12.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
time flies 🐦
Sure, will try to figure out a way to test it! |
8e307ea
to
615eb4c
Compare
This commit updates the fuzz testing framework to adapt to recent changes in the Parsec service code, allowing us to run the fuzzer within the same container that we use for CI. Signed-off-by: Ionut Mihalcea <ionut.mihalcea@arm.com>
Short test is now part of the CI |
Perfect! |
This commit updates the fuzz testing framework to adapt to recent
changes in the Parsec service code, allowing us to run the fuzzer within
the same container that we use for CI.
Signed-off-by: Ionut Mihalcea ionut.mihalcea@arm.com