Fixed and cleaned up TestIpfsStressRead

[hexdigest]

No description provided.

[Stebalien]

What's this trying to fix?

[hexdigest]

@Stebalien this stress test fails because it tries to read files using paths like this:
/tmp/fusetest413711254/ipfs/QmNst9wkM4mJNAFMzbLqUjPF2adxAcGACZYK2UxHgg6Tr7/child2/child0

while actual file path on a mounted filesystem doesn't have "/ipfs/" in it

Beside that if you run this test with -race flag enabled, you'll get "race: limit on 8192 simultaneously alive goroutines is exceeded, dying" error. This happens because nd.Context() is never being closed during the test and all go run() methods in session/sessionmanager/etc never exit which leads to goroutine leak (I'm going to fix it later)

This fix also adds more verbosity to test failure messages because when you send error to the channel you loose information about the line where this error occured and there are 6 lines where this can happen.

[Stebalien]

Ah, got it.

The first two fixes sound good but t.Run/t.Parallel probably aren't the right tools here. They're designed for running tests in parallel to speed them up. However, we're trying to run these tests in parallel to stress-test. That is, we want them to run in parallel with each other but nothing else.

(note: as-is, the t.Parallel call need to be moved into the t.Run for it to work correctly, but that would cause the test to exit before the subtests tests finish running).

[hexdigest]

@Stebalien
I put back initial implementation with goroutine. Some tests are failing but It doesn't seem like it's related to the changes I made.