*update: it does appear to only occur for debug build, so I assume* that unit tests are not typically run in debug. The root of most of the failures seem to be the Assumes.NotNull() helper for asserts being misplaced. So, though it is not failing on release builds, it is possibly not executing as expected.
Example: NetMqPollerTest.RemoveSocket() hits M-handle null check before it is ever created:
This issue has been automatically marked as stale because it has not had activity for 365 days. It will be closed if no further activity occurs within 56 days. Thank you for your contributions.
Environment
Expected behaviour
Unit tests run and pass
Actual behaviour
Many tests fail
Steps to reproduce the behaviour
Run unit tests.
Is this expected on the current master branch?
*update: it does appear to only occur for debug build, so I assume* that unit tests are not typically run in debug. The root of most of the failures seem to be the
Assumes.NotNull()
helper for asserts being misplaced. So, though it is not failing on release builds, it is possibly not executing as expected.Example:
NetMqPollerTest.RemoveSocket()
hitsM-handle
null check before it is ever created:Src link.