-
Notifications
You must be signed in to change notification settings - Fork 226
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
Improve test coverage. #1069
Improve test coverage. #1069
Conversation
Try and get all the special_functions/a*.hpp files up to 100%.
Refs #1068 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1069 +/- ##
===========================================
+ Coverage 85.24% 88.32% +3.07%
===========================================
Files 875 762 -113
Lines 66568 64394 -2174
===========================================
+ Hits 56745 56875 +130
+ Misses 9823 7519 -2304
... and 203 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Remove I0 initializers and rely on C++11 thread safe static const initialization.
And don't try and run concept checks with test coverage collection.
Add some more tests for the code that can be reached.
Also fixes a bug in bessel_y_derivative_small_z_series corner case.
Improve overflow handling in the implementations themselves.
Kill some unused variable warnings. Mark up code we think is unreachable but aren't sure about.
Dude it's massive +3 persent in one swath! |
Fixed Conflicts: test/Jamfile.v2 test/condition_number_test.cpp
OK folks, I hope this tranche of coverage improvement is good to go, I'll start a fresh PR for any more before the changes here get out of hand. @NAThompson there are a couple of drone failures in random_search_test which appear unrelated - tolerance too tight, or something non-deterministic in there? |
@jzmaddock : I noticed that yesterday and provided what I hoped was a fix; looks like I didn't quite get it. I recommend merging over the failure and I'll hopefully figure this one out pretty quick . . . |
done. merged. Thank you John. |
Ughhhh wait a minute. I just merged your branch. Not mine. |
I guess I need to revert that commit? I hope I did not turn this into a mess. |
Should be OK ;)
OK lets see what happens on develop |
Should be OK unless someone notices any SNAFU's. |
Indeed. I would just end up fumbling the fumble. I will merge my dos to develop. Then we just have the remaining very few test failures. |
Thanky you John! Probably, with your expert help (as usual) we can dig out of this. OK, so finally, I merged the new docs. This contains all your new coverage stuff. The docs look good, but the very few test failures are still present. |
As far as I can tell, everything is now OK on develop. @NAThompson triggered a few runs in his new work in #1083, and drone, GHA are OK there. Thanks again @jzmaddock, and sorry about the back-and-forth. |
Try and get all the special_functions/a*.hpp files up to 100%.