cerc-io/lotus
10
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 27 Wiki Activity

Merge pull request #6862 from filecoin-project/fix/racy-TestSimultanenousTransferLimit

Browse Source 
fix racy TestSimultanenousTransferLimit.
This commit is contained in:
Jakub Sztandera 2021-07-26 20:33:28 +02:00 committed by GitHub
commit acc38817ec
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
itests/deals_concurrent_test.go
View File

@ -190,7 +190,21 @@ func TestSimultanenousTransferLimit(t *testing.T) {
cancel() cancel()
wg.Wait() wg.Wait()
require.LessOrEqual(t, maxOngoing, graphsyncThrottle) // The eventing systems across go-data-transfer and go-graphsync
// are racy, and that's why we can't enforce graphsyncThrottle exactly,
// without making this test racy.
//
// Essentially what could happen is that the graphsync layer starts the
// next transfer before the go-data-transfer FSM has the opportunity to
// move the previously completed transfer to the next stage, thus giving
// the appearance that more than graphsyncThrottle transfers are
// in progress.
//
// Concurrency (20) is x10 higher than graphsyncThrottle (2), so if all
// 20 transfers are not happening at once, we know the throttle is
// in effect. Thus we are a little bit lenient here to account for the
// above races and allow up to graphsyncThrottle*2.
require.LessOrEqual(t, maxOngoing, graphsyncThrottle*2)
} }
runTest(t) runTest(t)