The specific tests I included (not sure why they got dropped before) do pass, though we're still waiting on the rest of the unrelated test suite. I also need to add tests/doc to stan-dev/stan. I'd love to see it go in for 2.7.1 since it's so close to being done and the rest is just grunt work. I should be able to get it done this week.
Krzysztof
>
> * advi-adapt-eta unit tests failing
>
> If you feel strongly about either of these being in 2.7.1, speak up now!
>
> No rush on my part and it doesn't matter to me if either of the
> above are in 2.7.1. But I do think they shouldn't go in without
> tests passing.
>
> - Bob
>
As far as I understood, you plan to advertise with 2.7.1 the autodiff library, so maybe this is of interest in this context: Currently the issue
https://github.com/stan-dev/math/issues/133
is still open. It describes test failures of g++ 4.4.7 & Intel compilers in stan-math. The g++ 4.4.7 is part of RedHat Linux Enterprise 6.5 which is installed in many production systems.
Moreover: Are those tests which fail critical? Can I not trust stan if those tests above fail with my compiler? Is there somewhere some information where users can get such information (how severe a failing stan-math test is with their compiler)?
Best,
Sebastian
On Tuesday, September 1, 2015 at 9:29:27 PM UTC+2, Bob Carpenter wrote:
> It's that grunt work that separates working code from
> research projects! We appreciate it.
>
> - Bob
>
>
> > On Aug 31, 2015, at 9:47 PM, Krzysztof Sakrejda
> >
The MKL+Intel is more sensitive than other configurations, yes. But note that I reported also results for Intel without MKL and for the g++ 4.4.7 without the MKL. So there are issues which affect RHEL6.5 installations which use g++ 4.4.7 as it was reported in the issue.
BTW, I have disabled MKL in all tests here run with stan-math.
Sebastian