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

Change Jazzer.js fuzz tests to fixed number of runs #321

Merged
merged 1 commit into from
Feb 20, 2023

Conversation

0xricksanchez
Copy link
Contributor

@0xricksanchez 0xricksanchez commented Feb 13, 2023

Trying to speed up CI runs by limiting the number of runs. Doesn't seem to have much of an impact (maybe 2–3 minutes shaved off for the fuzz test runner). The main waste of time happens on the Windows/macOS runner when building the native part each time. Caching builds seems to be the one factor that could be quite beneficial. I played around with this already, but couldn't make it work quite yet (FUZZ-575... branch).

Note: It's worth noting that we could reduce the number of runs to e.g. 10000 to lower the runtime even more, that said with 10k runs the fuzz test failed as they expect an error in some cases and as long as we don't fix the Windows/macOS runner it's wasted time.

@0xricksanchez 0xricksanchez marked this pull request as draft February 13, 2023 16:50
@0xricksanchez 0xricksanchez force-pushed the FUZZ-574_limit_fuzz_runs branch 3 times, most recently from c220da6 to 649a5c6 Compare February 15, 2023 13:41
@0xricksanchez 0xricksanchez marked this pull request as ready for review February 15, 2023 13:50
@0xricksanchez 0xricksanchez force-pushed the FUZZ-574_limit_fuzz_runs branch 2 times, most recently from f39981a to 6c0099c Compare February 15, 2023 13:52
@0xricksanchez 0xricksanchez reopened this Feb 15, 2023
@0xricksanchez 0xricksanchez requested a review from a team February 15, 2023 14:32
@bertschneider
Copy link
Contributor

Tests in the test folder still use max_total_time. We should also switch those to runs to make them more stable.

@0xricksanchez 0xricksanchez force-pushed the FUZZ-574_limit_fuzz_runs branch 2 times, most recently from b31f3db to 7c9de19 Compare February 20, 2023 10:27
@0xricksanchez 0xricksanchez force-pushed the FUZZ-574_limit_fuzz_runs branch 2 times, most recently from 186b3cf to 082da6f Compare February 20, 2023 11:33
@0xricksanchez 0xricksanchez added this pull request to the merge queue Feb 20, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 20, 2023
@0xricksanchez 0xricksanchez added this pull request to the merge queue Feb 20, 2023
Merged via the queue into main with commit d0d9f73 Feb 20, 2023
@0xricksanchez 0xricksanchez deleted the FUZZ-574_limit_fuzz_runs branch February 20, 2023 12:20
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.

None yet

2 participants