These are chat archives for boostorg/hana

18th
Dec 2015
Jason Rice
@ricejasonf
Dec 18 2015 20:02 UTC
Do you know how to get cmake to look for ruby in /usr/local/bin ?
Louis Dionne
@ldionne
Dec 18 2015 20:08 UTC
Hmm, it should probably look in that place on its own.
1 minute
Jason Rice
@ricejasonf
Dec 18 2015 20:10 UTC
oh sorry.. I had to remove CMakeCache.txt I think
I was thinking there was a RUBY_ROOT option or something
Louis Dionne
@ldionne
Dec 18 2015 20:11 UTC
I don’t see any RUBY_ROOT option in the documentation of the FindRuby.cmakemodule. If it does not work ,you can try adding /usr/local/bin to CMAKE_FIND_ROOT_PATH.
Jason Rice
@ricejasonf
Dec 18 2015 20:17 UTC
heh.. I apt-get remove --purge ruby'd and then realized it was probably just stuck in CMakeCache.txt.
Louis Dionne
@ldionne
Dec 18 2015 20:21 UTC
Does it work now?
Jason Rice
@ricejasonf
Dec 18 2015 20:22 UTC
yep
sorry to bother you
Louis Dionne
@ldionne
Dec 18 2015 20:26 UTC
No problem, really. The benchmarking system isn’t the prettiest thing, so don’t hesitate to let me know if you don’t understand or run into problems.
And if you have ideas to improve it, let me know.
Jason Rice
@ricejasonf
Dec 18 2015 21:48 UTC
is there a limit to size on your static doc site?
var hana = github.getRepo('boostorg', 'hana');
    hana.getRef('heads/datasets', function(err, sha) {
      var repo = "https://cdn.rawgit.com/boostorg/hana/" + sha + "/release/clang-3.6.2/";
      $(".benchmark-chart").each(function(index, div) {
        var dataset = div.getAttribute("damplement efficiently, because it requires stopping at the first element which satisfies the given predicate. For the same reason, modern techniques don't really help us here, so this algorithm constitutes a good test of the implementation quality of Hana, without taking into account the free lunch given to use by C++14.
          Number of elementsTime (s)Compile-time behavior of findta-dataset");
        $.getJSON(repo + dataset, function(options) {
          Hana.initChart($(div), options);
        });
      });
that div.getAttribute argument looks awfully suspicious
Jason Rice
@ricejasonf
Dec 18 2015 21:55 UTC
It looks like repo points to an absolute url which means the charts aren't coming from the same build
Louis Dionne
@ldionne
Dec 18 2015 21:57 UTC
The charts in the documentation are always pointing to the latest charts. I know, this is wrong.
Couldn’t figure out how to do it differently.
But I can’t find that div.getAttribute, where is it?
What this "damplement efficiently, because it require…”?
Jason Rice
@ricejasonf
Dec 18 2015 21:58 UTC
lol.. I was guessing that it is some kind of code generation bug
an attribute name is like class or style or something :laughing:
Louis Dionne
@ldionne
Dec 18 2015 21:59 UTC
Where did you find this?
Jason Rice
@ricejasonf
Dec 18 2015 21:59 UTC
the top of index.html
yeah the prod site actually says var dataset = div.getAttribute("data-dataset");
Louis Dionne
@ldionne
Dec 18 2015 22:05 UTC
My local build/doc/index.html is also fine, showing ”data-dataset”.
Jason Rice
@ricejasonf
Dec 18 2015 22:05 UTC
it's also statically set in header.html..
Louis Dionne
@ldionne
Dec 18 2015 22:06 UTC
Disregard the generated documentation. What you need to look at is the doc/ subdirectory. There, you’ll find header.html which is pulled in a the top of each html page by Doxygen.
Jason Rice
@ricejasonf
Dec 18 2015 22:08 UTC
sorry, I think the cat walked across the keyboard or something.. no idea how that got there
What if we pull the benchmark json files into the web root?
Jason Rice
@ricejasonf
Dec 18 2015 22:16 UTC
or should I say "would it be okay?"
Louis Dionne
@ldionne
Dec 18 2015 22:28 UTC
Yes, it would, but how would you do that? The benchmarks are generated on Travis CI in a separate job as the documentation job.
Jason Rice
@ricejasonf
Dec 18 2015 22:31 UTC
Ah, I see. Actually I just wanted to make an easy way to view all of the benchmarks, but since it is possibly comparing across builds perhaps it should be an external thing anyways.
Louis Dionne
@ldionne
Dec 18 2015 22:33 UTC
I think it should be stored externally like on AWS ideally, but I’m also not sure it’s worth the time to set this up, since I don’t know how.
We should associate every version of the documentation to specific benchmarks, though.
Jason Rice
@ricejasonf
Dec 18 2015 22:35 UTC
store what externally?
json files?
Louis Dionne
@ldionne
Dec 18 2015 22:38 UTC
The benchmarks, sorry.
Yes, basically.
Or they could also be straight on gh-pages. Actually… I have an idea. I’ll check it out tomorrow.
Jason Rice
@ricejasonf
Dec 18 2015 22:43 UTC
k