<p>As an update, I looked into the issue. It's not actually Mac-specific. Instead, the issue is more of a bad tolerance in those three failing tests. If I vary the random seed (which is, in these cases, set at compilation time), I sometimes get tests that pass and sometimes get tests that fail. For now what I would do in your packaging situation is to apply a patch that comments out those tests (either the entire test in svd_batch_test.cpp and svd_incremental_test.cpp, or just the lines that call <code>BOOST_REQUIRE_*</code>). I'm relatively sure the algorithms themselves will still work. Many of the mlpack tests are aimed more at ensuring that a code update does not break the functionality of the method, instead of ensuring that mlpack's algorithms work on every possible platform (in general, this is a lot harder to test and also failures of this type happen a lot less often).</p>
<p>I'm going to leave the ticket open until I fix the tests in master, but what I've written should be good enough to solve the Homebrew issue, I think.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/mlpack/mlpack/issues/417#issuecomment-77775016">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AJ4bFO8JaE88kDQVAvbyP33NCyIVMRrgks5nzLR0gaJpZM4DpNFg.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
<link itemprop="url" href="https://github.com/mlpack/mlpack/issues/417#issuecomment-77775016"></link>
<meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>