test: Array.create is deprecated; use Array.make

Signed-off-by: David Scott <dave.scott@citrix.com>
test: perform the write-then-read test with interesting buffer sizes

We know that the protocol does different things depending on the
client's choice of read and write buffer sizes.

This test currently fails.

Signed-off-by: David Scott <dave.scott@citrix.com>
Client and server now map the same buffers

  - make a Location.t which represents the location of a ring
  - Location.of_lengths picks two suitable non-overlapping locations
  - the server decides the locations and the client uses the
    server-provided settings

Signed-off-by: David Scott <dave.scott@citrix.com>
Regenerate oasis

Signed-off-by: David Scott <dave.scott@citrix.com>
Merge pull request #40 from djs55/more-tests

All interesting buffer size tests now pass
test: check that all resources are cleaned up afterwards

This test currently fails because event channels are leaked.

Signed-off-by: David Scott <dave.scott@citrix.com>
Close event channels

Signed-off-by: David Scott <dave.scott@citrix.com>
test: check for duplicate attempts to map the same grant

Signed-off-by: David Scott <dave.scott@citrix.com>
test: check I can read; write as well as write; read

Signed-off-by: David Scott <dave.scott@citrix.com>
test: check write wraps around the ring properly

Note the subtlety surrounding 'read': it returns a reference to
the data in the ring and doesn't consume it until the next read.

Signed-off-by: David Scott <dave.scott@citrix.com>
test: create and use a 'with_connection' function

Signed-off-by: David Scott <dave.scott@citrix.com>
test: check read before write in both directions

Signed-off-by: David Scott <dave.scott@citrix.com>
Merge pull request #41 from djs55/more-tests

Test that resources are cleaned up