Benjamin Wang

test golangci

[test] TestBalancerUnderNetworkPartitionDelete failure

1

Raised on the latest code on `main` branch. ``` === FAIL: integration/clientv3/connectivity TestBalancerUnderNetworkPartitionDelete (8.12s) cluster.go:532: Creating listener with addr: 127.0.0.1:2109805817 ...... logger.go:130: 2022-08-10T22:44:54.878Z WARN m1 request stats {"member": "m1", "start...

Raised on the latest code on `main` branch. ``` --- FAIL: TestOpenWithMaxIndex (0.00s) testing.go:967: TempDir RemoveAll cleanup: unlinkat /tmp/TestOpenWithMaxIndex2918559458/001: directory not empty ``` Refer to https://github.com/etcd-io/etcd/runs/7777195247?check_suite_focus=true

Add integration test for etcd tracing

2

We can follow the same way as Kubernetes did in [pull/103234](https://github.com/kubernetes/kubernetes/pull/103234). It's also the prerequisite to graduate/stable the experimental tracing flags. [12460](https://github.com/etcd-io/etcd/issues/12460)

[3.4] panic: runtime error: invalid memory address or nil pointer dereference

18

I saw this error multiple times in 3.4 pipeline, ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xab2922] goroutine 3500 [running]:...

[Improvement] Use workspace mode to simplify the go.mod

4

Currently there is lots of replace directives in each go.mod file, and most of them are some duplicated items. In golang 1.18 to be release early next year, a new...

[3.4] panic: runtime error: index out of range [0] with length 0 [recovered]

5

The issue was found in 3.4 pipeline. ``` --- FAIL: TestWatchReconnRequest (1.12s) panic: runtime error: index out of range [0] with length 0 [recovered] panic: runtime error: index out of...

[3.4] ./test: line 229: kill: (7520) - No such process

5

I saw this error multiple times in 3.4 pipeline, ``` {"level":"info","ts":1658452719.9775898,"caller":"tester/cluster.go:585","msg":"closed tester HTTP server","tester-address":"127.0.0.1:9028"} ./test: line 229: kill: (7520) - No such process ./test: line 229: kill: (7521) - No...

Print clusterID, memberID and leaseID in hexdecimal

5

ClusterID, memberID and leaseID are just identities, so it doesn't make sense to print them in decimal. Instead, we should always print them in hexadecimal. Please note the existing behavior...

[test] Add test cases to cover the case that client api version is not valid UTF-8 string

2

This is a supplement task for [pull/13560 ](https://github.com/etcd-io/etcd/pull/13560 )