Re: [MirageOS-devel] Notes on testing

2015-05-06 Thread Anil Madhavapeddy
On 6 May 2015, at 02:29, Thomas Leonard wrote: > > On 6 May 2015 at 10:18, Mindy wrote: >> Thanks for writing these up :) progress notes: >> >> On 05/06/2015 01:31 AM, Richard Mortier wrote: >>> >>> >>> [mort]: Document that `mirage-net-pcap` should be used to gather >>> `.pcap` files for a b

Re: [MirageOS-devel] Notes on testing

2015-05-06 Thread Richard Mortier
Probably... http://conferences.sigcomm.org/sigcomm/2005/paper-BisFai.pdf for those who've not seen it. On 6 May 2015 at 03:19, Jon Crowcroft wrote: > Worth re-reading peter Sewell's SIGCOMM paper on TCP? > > On 6 May 2015 01:32, "Richard Mortier" wrote: >> >> A little late, but finally got roun

Re: [MirageOS-devel] Mirage fortnightly call - Wednesday 6th at 4pm BST

2015-05-06 Thread Amir Chaudhry
Hi folks, the Hangout URL is https://plus.google.com/hangouts/_/gq7e36svyh3okzlban3s65nwnya AC > On 5 May 2015, at 17:49, Amir Chaudhry wrote: > > Hi folks, > > The next Mirage call will take place on Wednesday afternoon at 4pm BST and is > open to all. We'll be on Google Hangout this time

[MirageOS-devel] MirageOS Puppet module

2015-05-06 Thread Gareth Rushgrove
As mentioned a few days ago, I've just pushed an initial release of a Puppet module to install OCaml, OPAM and Mirage. https://github.com/garethr/garethr-mirageos https://forge.puppetlabs.com/garethr/mirageos This currently supports Ubuntu 12.04 and 14.04. If you have Puppet installed then gettin

Re: [MirageOS-devel] test, quality, tcpip

2015-05-06 Thread Thomas Gazagnaire
Thanks for your email Mindy! > We should also 1) figure out which of the error exposing/handling proposals > won and 2) start using whichever one it is. I had a first experimentation[1] with the new error handling based on Rresult[2]. The branch needs to be rebased and need more feedback, but I

Re: [MirageOS-devel] Notes on testing

2015-05-06 Thread Jon Crowcroft
Worth re-reading peter Sewell's SIGCOMM paper on TCP? On 6 May 2015 01:32, "Richard Mortier" wrote: > A little late, but finally got round to writing up some notes on the > conversation a couple of weeks ago on how we might approach testing in > Mirage. > > """ > # Notes > > + Testing is used for

Re: [MirageOS-devel] test, quality, tcpip

2015-05-06 Thread Justin Cormack
On 6 May 2015 at 10:40, Mindy wrote: > - improve and formalize (create?) error communication for bad state > transitions, syntactically OK but semantically bogus packets, etc The only useful error communication I can think of is counters of types of error, which you can use when deliberately te

[MirageOS-devel] test, quality, tcpip

2015-05-06 Thread Mindy
Hi folks, Mort's writeup of notes from a conversation on testing raises some questions on how to actually go about testing `tcpip`. I'm starting a new thread to avoid potentially hijacking a more general conversation on testing with this rather more specific proposal, but most of what I'm di

Re: [MirageOS-devel] Notes on testing

2015-05-06 Thread Thomas Leonard
On 6 May 2015 at 10:18, Mindy wrote: > Thanks for writing these up :) progress notes: > > On 05/06/2015 01:31 AM, Richard Mortier wrote: >> >> >> [mort]: Document that `mirage-net-pcap` should be used to gather >> `.pcap` files for a bug report. > > I'll soon release a version of `mirage-net-pcap`

Re: [MirageOS-devel] Notes on testing

2015-05-06 Thread Mindy
Thanks for writing these up :) progress notes: On 05/06/2015 01:31 AM, Richard Mortier wrote: [mort]: Document that `mirage-net-pcap` should be used to gather `.pcap` files for a bug report. I'll soon release a version of `mirage-net-pcap` that plays nicely with `mirage-vnetif` rather than rei