Comment 5 for bug 1813147

The

    b'Short read - got 167 bytes, wanted 4263 bytes'

error message comes from here [0].

However recent failure[1][2][3] shows a different message:

    Not a text type application/octet-stream

This message comes from [4].

All of this points towards that something strange is printed to the test output that confuses ourt tooling.

I've tried to simply recreate the problem by logging extensively from a test case but that leads to a different error:

     Length too long: 16814020

[0] https://github.com/testing-cabal/subunit/blob/58c3d364266e7550d3e00e34191eed7df2d36d13/python/subunit/v2.py#L418
[1] http://logs.openstack.org/17/573317/48/check/openstack-tox-lower-constraints/08b08c1/job-output.txt
[2] http://logs.openstack.org/28/619528/12/check/openstack-tox-lower-constraints/1d86436/job-output.txt
[3] http://logs.openstack.org/23/630723/3/check/nova-tox-functional-py35/560139d/job-output.txt
[4] https://github.com/testing-cabal/testtools/blob/f865cfefae73e540aedb16ebb19f813cc648f2b6/testtools/content.py#L108