On 29 Oct 2015, at 17:37, Thomas Gazagnaire wrote:
>
>> This is similar to the existing mirage/mirage-flow repo, only for `BLOCK`.
>>
>> Let me know what you think!
>
> That's very useful. Would also useful be useful if we have unit-tests
> functors that BLOCK implementation can instantiate to
> This is similar to the existing mirage/mirage-flow repo, only for `BLOCK`.
>
> Let me know what you think!
That's very useful. Would also useful be useful if we have unit-tests functors
that BLOCK implementation can instantiate to check that they are correct.
Haven't done that for mirage-flow
On 10/29/2015 05:00 PM, Thomas Leonard wrote:
On 29 October 2015 at 16:45, Rupert Horlick wrote:
Hi Thomas,
I’ve just been adding unit tests to my Mirage application using OUnit, but they
started throwing up errors.
I found your patch for the problem here
(http://forge.ocamlcore.org/tracker
> I guess oUnit is dead (that patch was first submitted in 2013). Maybe
> one of the other frameworks would be better, although the work-around
> is OK if you don't need to run tests in parallel. Mirage has alcotest,
> although I haven't used it in my own code:
>
> https://github.com/mirage/alcote
On 29 October 2015 at 16:45, Rupert Horlick wrote:
> Hi Thomas,
>
> I’ve just been adding unit tests to my Mirage application using OUnit, but
> they started throwing up errors.
>
> I found your patch for the problem here
> (http://forge.ocamlcore.org/tracker/index.php?func=detail&aid=1363&group
Hi,
FYI I just found myself writing a generic `copy` function over `BLOCK`
devices for about the 100th time so I've created a repo called
`mirage-block` to contain generic functions over block devices. The kinds
of things I have in mind are:
1. copy
2. erase
3. mirror
4. Linux device-mapper like
