failing Travis-CI builds

[wilx]

I have read your twee and took a look and seen that https://travis-ci.org/ericniebler/range-v3 shows the build failing on a static_assert.

[ericniebler]

I've removed the link to the travis build from the readme. The travis support has fallen into disrepair. I run all tests locally on gcc 4.9 and clang-trunk with libstdc++ before I commit, so I'm reasonably certain the code works.

Gonzalo, if you're reading this, perhaps you'd be willing to give Travis another go?

[gnzlbg]

@ericniebler thanks for removing the link, i'll try to get libc++ running again on the Travis-VMs ASAP.

[ericniebler]

BTW, the static_assert is failing on clang-3.4, but not clang-3.5. I'm not sure if travis has clang-3.5. That's the version I test on.

[ericniebler]

Update: I fixed the static_assert issue and worked around a few issues that were giving clang 3.4 fits. Tests pass locally with clang 3.4 for me, but strangely not on Travis. Go figure.

[gnzlbg]

@ericniebler it seems that libc++ is working fine under travis again (without me changing anything). The clang 3.4 used in travis (I guess 3.4.0) can't handle some stuff in some testcases. I'm trying to find exactly what it cannot handle.

UPDATE: It only fails in debug mode :/

[ericniebler]

If I had to guess, I'd say the problem is that the tests that are failing to build (the set_* algorithm tests) are causing memory usage to spike, and the VM is just too limited. Compiler runs out of memory and . I can see about writing these tests in a more efficient way.

[ericniebler]

Managed to get a Travis build to pass. It's clear I need to redesign the make_testable test component though, since it's causing an explosion in the number of template instantiations.