Fix some issues with new tests locking in bug fixes #17320
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I did not think to run memleaks testing on these tests, and hadn't
realized that they hadn't freed their unmanaged classes. Do so here.
There was a portability issue on linux32 due to casting a c_void_ptr
to a 64-bit integer. I've rewritten the test to avoid the cast, which
I believe should resolve the issue, and via inspection of the generated
code it seems to. That said, due to a lack of time today, I haven't
had the chance to run the test on linux32, so am relying on the nightly
run to do that where, if I haven't fixed it, there shouldn't be any new
noise.