apache / apache/pulsar-client-go
[BUG] Execution of go test is blocked
- Dominant language
- Go
- Stars
- 745
- Forks
- 389
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 3
Description
#### Expected behavior
> go test ./...
Execute go test correctly, whether it passes or not.
#### Actual behavior
After executing go test, the command will not complete.
This affects not only the results of executing within this repository, but also go projects that have been introduced to this repository.
```
(base) [root@iZt pulsar-client-go]# go mod download
(base) [root@iZt pulsar-client-go]# go test ./...
? github.com/apache/pulsar-client-go/examples/consumer [no test files]
? github.com/apache/pulsar-client-go/examples/consumer-listener [no test files]
? github.com/apache/pulsar-client-go/examples/producer [no test files]
? github.com/apache/pulsar-client-go/examples/reader [no test files]
? github.com/apache/pulsar-client-go/integration-tests/pb [no test files]
? github.com/apache/pulsar-client-go/oauth2/cache [no test files]
? github.com/apache/pulsar-client-go/oauth2/clock [no test files]
? github.com/apache/pulsar-client-go/oauth2/clock/testing [no test files]
? github.com/apache/pulsar-client-go/oauth2/store [no test files]
ok github.com/apache/pulsar-client-go/oauth2 3.039s
? github.com/apache/pulsar-client-go/perf [no test files]
? github.com/apache/pulsar-client-go/pulsar/internal/crypto [no test files]
? github.com/apache/pulsar-client-go/pulsar/internal/pulsar_proto [no test files]
? github.com/apache/pulsar-client-go/pulsar/log [no test files]
? github.com/apache/pulsar-client-go/pulsaradmin [no test files]
```
It's a perpetual waiting game.
#### Steps to reproduce
Pull the repository code and run the command on the master branch.
> go test ./...
#### System configuration
**Pulsar version**: master or v0.11.0
**go version**: go1.20.3 linux/amd64 or go1.20.6 darwin/arm64
**OS**: macOS m2 or linux centOS7
Contributor guide
Research direction
Reproduce the hang with `go mod download` followed by `go test ./...` on the master branch, using the Go and operating-system versions reported in the issue. Investigate which package or test blocks after the displayed output; done means the full command completes rather than waiting indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100