A simple `make` should not run very long tests about celero HOT 4 CLOSED

Agreed that the long test is not helpful. Initially, the running of the benchmarks after the build was to demonstrate how to integrate Celero into a build environment in a way analogous to a unit test framework. However, since then some examples have been added that take a very long time to run. It seems reasonable to exclude long tests from the auto run or to have only one simple test auto-run to demonstrate the functionality.

from celero.

I now tried the celeroDemoSort demo, but on my Intel i7 with 2.6 GHz it runs for hours.
It would be nicer to have examples that finish within seconds or minutes at most so that I can run them quickly and see the output.
I don't want to wait until the next day to continue learning Celero. :-(

from celero.

Agreed. I used the long run for an article...but will change the default problem set size to execute in a reasonable time for this demo. Thanks for the note.

I notice that you are running with Clang, and I have not tested with Clang. Have you had any other issues or oddities?

from celero.

Everything in Celero works with clang.

I think this was to be expected, since it's C++11 feature-complete (see here) and can be used as a drop-in replacement for gcc.

from celero.