Reduce the time e2e tests take · etcd-io/etcd#18983

(34 留言) (0 反應) (1 負責人)Go (51,701 star) (10,352 fork)batch import

area/testinghelp wantedtype/feature

描述

E2e tests are taking over 40 minutes now, we should keep them unver 30 minutes or even lower.

Current state

go.etcd.io/etcd/tests/v3/common.TestMemberAdd > 5 minutes
go.etcd.io/etcd/tests/v3/common.TestMemberRemove > 2 minutes
go.etcd.io/etcd/tests/v3/e2e.TestAuthority > 1.5 minutes
go.etcd.io/etcd/tests/v3/e2e.TestRuntimeReconfigGrowClusterSize > 1 minute
go.etcd.io/etcd/tests/v3/common.TestUserAdd_Simple > 1 minute
go.etcd.io/etcd/tests/v3/common.TestLeaseGrantAndList ~ 50 seconds
go.etcd.io/etcd/tests/v3/e2e.TestVerifyHashKVAfterCompact ~50 seconds
go.etcd.io/etcd/tests/v3/e2e.TestMixVersionsSnapshotByMockingPartition ~ 40 seconds
go.etcd.io/etcd/tests/v3/common.TestKVDelete ~ 40 seconds
go.etcd.io/etcd/tests/v3/common.TestLeaseGrantTimeToLiveExpired ~ 35 seconds
go.etcd.io/etcd/tests/v3/e2e.TestWatchDelayForManualProgressNotification ~ 35 seconds ...

Looking for someone to take a look at the top tests and propose improvements to reduce runtime

We should keep the test execution time low to ensure good contributor expirience.

技術棧: go
領域: testingperformance
議題類型: performance
難度: 4
預計時間: 1-2 days
活動狀態: active
清晰度: clear
前置要求: Goe2e testingetcd codebase
新手友善度: 35
研究方向: Examine the top slow tests listed in the issue, particularly TestMemberAdd (over 5 minutes) and TestMemberRemove (over 2 minutes). Investigate why these tests are slow by looking at the test code in the tests/v3/common and tests/v3/e2e directories. Propose optimizations such as reducing setup overhead, parallelizing test steps, or using lighter test fixtures. The issue comments may contain hints; check https://testgrid.k8s.io/sig etcd periodics for historical duration graphs.