Mirage itself is ISC licensed (I've created an issue to add it to the main tool repository). I don't believe there are any licensing issues since we only run Bisect at build time to generate a report, and it's not otherwise linked or distributed with the library that it is bisecting.
-anil > On 4 May 2015, at 12:14, Ashish Agarwal <[email protected]> wrote: > > Bisect is GPL. Is it compatible with Mirage's license? BTW, what is Mirage's > license? I don't see it in the main repo <https://github.com/mirage/mirage>. > > On Thu, Mar 12, 2015 at 5:34 AM, David Scott <[email protected] > <mailto:[email protected]>> wrote: > Hi, > > I've been having a lot of fun with bisect[1] recently-- I've been using it to > see which parts of the mirage-block-volume[2] and shared-block-ring[3] > libraries are completely untouched by their unit tests. I found the following > game to be quite addictive: > > 1. "make coverage", and load result in web-browser > 2. spot a big chunk of obvious red (danger, danger, danger) > 3. (thinking carefully about what could go wrong) devise an interesting test > to stress the red bits (obviously you could cover it with a 'noddy' test but > there is probably no point) > 4. "make coverage", reload in browser and see the red go green! > > I've hooked it up with coveralls.io <http://coveralls.io/> (admittedly in a > bit of a hacky way[4]) such that the master branch is firmly in "development" > mode, linking against bisect, and without checking in the oasis autogen > rubbish. The .travis.yml runs both the travisci-skeleton script and then > invokes ocveralls[5] to upload the results. > > I've added a separate "make release" step which removes bisect and checks in > the autogen (presumably into a release branch). Perhaps eventually this could > make a github pull request (with the "hub" tool?) and make an opam package? > > I think the game is made even more addictive when the coveralls badge changes > colour, see: > > https://coveralls.io/r/mirage/mirage-block-volume?branch=master > <https://coveralls.io/r/mirage/mirage-block-volume?branch=master> > > Here's an example bisect report (the code is a work-in-progress): > > http://dave.recoil.org/tmp/report/file0000.html > <http://dave.recoil.org/tmp/report/file0000.html> > > If you haven't given bisect a go -- I recommend playing with it. > > Also, if you can think of a nicer way to integrate this -- I admit using > 'sed' on the _oasis file is a bit of a hack -- please let me know! > > Cheers, > Dave > > [1] http://bisect.x9c.fr <http://bisect.x9c.fr/> > [2] https://github.com/mirage/mirage-block-volume > <https://github.com/mirage/mirage-block-volume> > [3] https://github.com/mirage/shared-block-ring > <https://github.com/mirage/shared-block-ring> > [4] > https://github.com/mirage/shared-block-ring/commit/67b9f3100be8e4e9732dd79b7c1cc5352a61d478 > > <https://github.com/mirage/shared-block-ring/commit/67b9f3100be8e4e9732dd79b7c1cc5352a61d478> > [5] https://github.com/sagotch/ocveralls > <https://github.com/sagotch/ocveralls> > _______________________________________________ > MirageOS-devel mailing list > [email protected] > <mailto:[email protected]> > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > <http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel> > > > _______________________________________________ > MirageOS-devel mailing list > [email protected] > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
_______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
