Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: riemann port already in use #11117

Closed
powersj opened this issue May 17, 2022 · 0 comments · Fixed by #11118
Closed

test: riemann port already in use #11117

powersj opened this issue May 17, 2022 · 0 comments · Fixed by #11118
Labels
bug unexpected problem or unintended behavior

Comments

@powersj
Copy link
Contributor

powersj commented May 17, 2022

Relevant telegraf.conf

n/a

Logs from Telegraf

2022/05/17 12:17:01 Entering
--- FAIL: TestSocketListener_tcp (0.00s)
    riemann_listener_test.go:25: 
        	Error Trace:	riemann_listener_test.go:25
        	Error:      	Received unexpected error:
        	            	listen tcp 127.0.0.1:5555: bind: address already in use
        	Test:       	TestSocketListener_tcp
FAIL
FAIL	github.com/influxdata/telegraf/plugins/inputs/riemann_listener	0.049s

System info

master

Docker

No response

Steps to reproduce

  1. docker-compose up
  2. go test -count=1 -race -timeout 30s ./plugins/inputs/riemann_listener/...

Expected behavior

tests to pass

Actual behavior

If the docker compose containers are running, it means that a reimann listener is already setup on port 5555. Then in the input test it attempts to start a socket listener using the same port.

Additionally, only the outputs/riemann_legacy plugin even attempts to use the reimann listener that is set up by the docker compose script, and that single test is always skipped.

Additional info

No response

@powersj powersj added the bug unexpected problem or unintended behavior label May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant