Skip to content

/prometheus

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

TestTargetScrapeWithFullChannel is flaky #1081

Closed
brian-brazil opened this Issue Sep 14, 2015 · 2 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@brian-brazil
@brian-brazil
Copy link
Member

brian-brazil commented Sep 14, 2015

I see this one every now and then:

--- FAIL: TestTargetScrapeWithFullChannel (0.01s)
        target_test.go:164: Expected target error "ingestion channel full", actual: "read tcp 127.0.0.1:58844->127.0.0.1:58409: i/o timeout"

I haven't had a chance to look into it yet
@brian-brazil

This comment has been minimized.

Sign in to view
Copy link
Member Author

brian-brazil commented Sep 14, 2015

My guess is that sometimes 10ms isn't enough time to do the scrape sometimes, I've seen this with 1.4.2 also so not a new GC issue. We probably need to bump that timeout.

@brian-brazil brian-brazil referenced this issue Sep 14, 2015

Closed

retrieval: Bump timeout beyond 256ms of test #1082

@brian-brazil brian-brazil referenced this issue Sep 22, 2015

Merged

retrieval: Reduce flakiness of target tests #1109

@brian-brazil brian-brazil closed this in #1109 Sep 23, 2015

@lock

This comment has been minimized.

Sign in to view
Copy link

lock bot commented Mar 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 24, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.