On Fri, Sep 22, 2017 at 11:48:02PM +0800, Shengjing Zhu wrote:
> I meet this FTBFS either.
> After looking at the code, I think it's caused by this test only waits
> 5s for writing 134M data.
> So I changed the time to 180s which I think sufficient for most disks.
> Since the upstream is not active now, I haven't reported it to upstream.
Hmm. Why would a test suite have to test the disk speed at all?
A test suite in a program is supposed to test the program,
not the underlying hardware.
IMHO; I don't think such kind of tests are really useful.
I would just disable the test completely.
Pkg-go-maintainers mailing list