Fix the Broken malloc_n Behavior#53
Conversation
|
@mclow Could you please approve me running the test workflow to see if it will pass the existing unit tests? |
Added Unit Tests
|
Also tagging @jzmaddock for enabling first-time user workflow. |
|
The patch works. Can someone please review and approve? Thank you. |
|
I've approved the run, but I'm not sure how up to date the CI scripts are. We've also often talked about marking this library deprecated, but that appears not to have happened yet :( |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #53 +/- ##
===========================================
+ Coverage 93.48% 93.71% +0.23%
===========================================
Files 9 9
Lines 583 589 +6
===========================================
+ Hits 545 552 +7
+ Misses 38 37 -1
Continue to review full report at Codecov.
|
@jzmaddock Do you still suggest merging this patch? There is a small coverage check failing which I shall further investigate. |
Add more unit tests.
I know it's a relatively trivial patch, but I still need to find the time to do a proper eyeball-checkover before merging. Please nag me if I don't get to it soon-ish. |
|
Thanks @jzmaddock. Take your time. Some of the new unit tests I added this morning trying to remedy the unit test coverage issues yesterday seems having some problems. I will check and try fixing them later today or tomorrow. |
|
@jzmaddock I tested the new patch I just uploaded locally and it worked. Hope this time the test coverage issue can be fixed. Is there anyway that I can measure the test coverage locally BTW? |
|
@jzmaddock Request running more test workflows. |
|
@jzmaddock With the new unit test, it added one additional coverage comparing to the previous commit cf9b5c4. But it's still missing one coverage comparing to the develop branch. Is it something that has to be fixed in order to get the pull request merged? Thanks. |
|
@jzmaddock Added one more unit test. I ran some local unit test to see if the logic will flow to the positions where the coverage test failed. It seems that it will help. Please run the test workflow again. Thanks. |
|
@jzmaddock It seems that it has passed all the checks. Could you please review and merge if possible? |
|
@jzmaddock Bothering you again :) |
|
@jzmaddock @pabristow Can some of you please review? |
|
This all checks out, thanks for persevering! |
Thank you very much! |
…rameter value) introduced with (boostorg#53)
…rameter value) introduced with (#53)
Fix #52 and added unit tests.