-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
tests: run fuzzers four times in a row #10794
Conversation
40c7cc4
to
0a22268
Compare
Judging by
it seems to be working. I'm tempted to create a label called "ci-fails/doesn't-need-rework" :-) I'll wait for #10793 to be merged, rebase it on top to see how it goes. |
This should help to catch issues that are easily detectable by bad_build_check like the one being fixed in systemd#10793, which would totally break the build tomorrow if I hadn't run `helper.py check_build` manually.
0a22268
to
4e0de26
Compare
Now that #10793 is merged, I rebased the PR on top of master to see how it goes. TravisCI and semaphorci should become green soon. |
@evverx Do you think it can be merged now? |
@@ -30,7 +35,8 @@ int main(int argc, char **argv) { | |||
} | |||
printf("%s... ", name); | |||
fflush(stdout); | |||
(void) LLVMFuzzerTestOneInput((uint8_t*)buf, size); | |||
for (int j = 0; j < MIN_NUMBER_OF_RUNS; j++) |
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.
BTW, I prefer here unsigned
or size_t
. But please ignore this now.
@yuwata yes, I think this PR is ready to roll. |
OK. Let's ignore remaining CIs. |
This should help to catch issues that are easily detectable by
bad_build_check like the one being fixed in #10793,
which would totally break the build tomorrow if I hadn't run
helper.py check_build
manually.