Looks like iotest package provides tools to simulate various weird read behaviors.
However, I want to simulate a failure, instead of just a slowdown or a change in whether the EOF error is returned after the last full read. Something like "ReadFailAfterN" which will trigger a non-EOF error after N bytes read.... Googling for various combinations of keywords hasn't gotten me very far, because "fail" and "error" come up too commonly. Anything out there? Eric. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
