I've tried to clean up the code, and pushed. Specifically: - the table code no longer uses a local hacked Tiny-Table (switched to 3.0.1) - the graph code is all in graph.js, and uses d3.v4
There are also two scripts: - testing/web/setup.sh which _might_ set things up - testing/web/publish.sh _should_ run the testsuite then publish the results; it is using testing/utils/json-*.py to generate the input json) Hopefully there's enough info for the motivated to set up their own testing web site and, well, fix it. OTOH. there must be an existing off-the-shelf test visualization tool available somewhere. On 13 July 2016 at 12:10, Paul Wouters <[email protected]> wrote: > Sounds good to me. > > Sent from my iPhone > >> On Jul 13, 2016, at 3:44 PM, Andrew Cagney <[email protected]> wrote: >> >> Hi, >> >> I'd like to put the key html files (i.e., i1.html, i2.html, i3.html, >> css?) used to create the test-result web site in a repository >> somewhere. My first thought is testing/web/ in the existing repo? >> I'd also like to avoid adding the javascript dependencies, and instead >> just use the unmodified upstream. >> >> thoughts, >> Andrew >> _______________________________________________ >> Swan-dev mailing list >> [email protected] >> https://lists.libreswan.org/mailman/listinfo/swan-dev _______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
