This issue was created by maloo for Andreas Dilger <andreas.dilger@intel.com>
This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/1d250bbe-f0c9-11e2-ba12-52540035b04c.

This test has been failing intermittently for at least a year, but has never had a bug opened for it. The first reported failure with this message is a single failure on 2012-01-05:
https://maloo.whamcloud.com/sub_tests/bea1ba98-37e1-11e1-bd0c-5254004bbbd3 (2012-01-05)

but there are a number of previous failures on the same test with "test_13 returned 1" starting on 2012-08-22 through 2013-04-23, as many as 3 or 4 failures a day. It then returned on 2013-06-04 with the current failure message:
https://maloo.whamcloud.com/sub_tests/bd93ded6-ccde-11e2-a1e0-52540035b04c

However, while that was the first recorded failure on an unlanded patch, there were many other failures on different patches before the first one landed several months later, so it was not the root cause.

There are no messages on the consoles of the client or MDS that would indicate the cause.

The sub-test test_13 failed with the following error:

f13 shouldn't return an error (1)

Info required for matching: sanityn 13