-
Notifications
You must be signed in to change notification settings - Fork 466
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
tools: option to run block generator test multiple times #5617
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5617 +/- ##
==========================================
+ Coverage 54.95% 54.97% +0.02%
==========================================
Files 460 460
Lines 64446 64446
==========================================
+ Hits 35417 35432 +15
+ Misses 26653 26644 -9
+ Partials 2376 2370 -6 see 13 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
Nice change!
Now that the generator has a verbose
flag, suggesting to use it for quieting some printouts, instead of commenting them out.
Co-authored-by: Zeph Grunschlag <[email protected]>
Summary
Optimizing for usage patterns. It is sometimes useful to run the same suite multiple times to account for transient DB behavior.
I'm using several scripts to run this tool. There may be other features from those scripts that should be migrated, but this seemed like a good start.
There are also some minor changes to logging to remove constant debug output and optimize for general usage.
Test Plan