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

all-in-one integration test is unstable #1583

Closed
yurishkuro opened this issue Jun 3, 2019 · 7 comments
Closed

all-in-one integration test is unstable #1583

yurishkuro opened this issue Jun 3, 2019 · 7 comments

Comments

@yurishkuro
Copy link
Member

Build failing https://travis-ci.org/jaegertracing/jaeger/jobs/540902708#L990

=== RUN   TestAllInOne
--- FAIL: TestAllInOne (1.01s)
    require.go:794: 
        	Error Trace:	all_in_one_test.go:86
        	            				all_in_one_test.go:60
        	Error:      	Received unexpected error:
        	            	Get http://0.0.0.0:16686/api/traces?service=jaeger-query&tag=jaeger-debug-id:debug: dial tcp 0.0.0.0:16686: connect: connection refused
        	Test:       	TestAllInOne
FAIL
FAIL	github.com/jaegertracing/jaeger/cmd/all-in-one	1.222s
make: *** [integration-test] Error 1

Looking at

func healthCheck() error {
for i := 0; i < 100; i++ {
if _, err := http.Get(queryURL); err == nil {
return nil
}
time.Sleep(100 * time.Millisecond)
}
return fmt.Errorf("query service is not ready")
}

it seems that it may not wait long enough for health check to become green. I would extend the loop to 10k iteration (10seconds).

@guanw
Copy link
Contributor

guanw commented Jun 3, 2019

Not sure about this.. Since the error was thrown on L86 where it was tryhing to getAPITrace instead of healthCheck. But I will try that in a bit.

@guanw
Copy link
Contributor

guanw commented Jun 3, 2019

Increase the loop count & sleep time don't work. I'm going to try that script on a linux vm environment see if I could reprod there.

@guanw
Copy link
Contributor

guanw commented Jun 4, 2019

Turns out this to be an issue with prometheus panic as it requires all categories sharing same structure (in this case, the tag set should also be the same) I made the fix in the original story.

@yurishkuro
Copy link
Member Author

are you sure? I thought I saw the same failure on master.

@guanw
Copy link
Contributor

guanw commented Jun 4, 2019

i think so. The test is passing now on #1576

@yurishkuro
Copy link
Member Author

OK, in that case this ticket is still relevant, in the sense that the integration test doesn't check something. For example, if your issue in #1576 was causing all-in-one to crash upon receiving a request, we should've seen it in the test somehow, e.g. by dumping logs from Docker.

@yurishkuro
Copy link
Member Author

have not seen this issue for a long time, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants