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: statsd.TestCachesExpireAfterMaxTTL timed out #12341

Closed
powersj opened this issue Dec 6, 2022 · 1 comment · Fixed by #12354
Closed

test: statsd.TestCachesExpireAfterMaxTTL timed out #12341

powersj opened this issue Dec 6, 2022 · 1 comment · Fixed by #12354
Assignees
Labels
bug unexpected problem or unintended behavior

Comments

@powersj
Copy link
Contributor

powersj commented Dec 6, 2022

Relevant telegraf.conf

na

Logs from Telegraf

=== FAIL: plugins/inputs/google_cloud_storage TestRunGatherIterationWithPages (unknown)
2022/12/05 19:02:27 D! [] Fetching key: prefix/1604148850991
2022/12/05 19:02:27 D! [] Fetching key: prefix/1604148850992
2022/12/05 19:02:27 D! [] Fetching key: prefix/1604148850993
2022/12/05 19:02:27 D! [] Fetching key: prefix/1604148850994
2022/12/05 19:02:27 I! [] Iterated all the keys
2022/12/05 19:02:27 I! [] Iterated all the keys
--- PASS: TestRunGatherIterationWithPages (0.06s)

=== FAIL: plugins/inputs/statsd TestCachesExpireAfterMaxTTL (unknown)
coverage: 79.6% of statements
panic: test timed out after 10m0s

goroutine 115 [running]:
testing.(*M).startAlarm.func1()
	C:/Program Files/Go/src/testing/testing.go:2036 +0xbb
created by time.goFunc
	C:/Program Files/Go/src/time/sleep.go:176 +0x48

goroutine 1 [chan receive, 9 minutes]:
testing.(*T).Run(0xc000085860, {0xcae176, 0x1b}, 0xce0a58)
	C:/Program Files/Go/src/testing/testing.go:1494 +0x789
testing.runTests.func1(0x0?)
	C:/Program Files/Go/src/testing/testing.go:1846 +0x9a
testing.tRunner(0xc000085860, 0xc00026fb68)
	C:/Program Files/Go/src/testing/testing.go:1446 +0x217
testing.runTests(0xc000364be0?, {0x118f7e0, 0x2e, 0x2e}, {0x40?, 0xc00026fc30?, 0x1199680?})
	C:/Program Files/Go/src/testing/testing.go:1844 +0x7ed
testing.(*M).Run(0xc000364be0)
	C:/Program Files/Go/src/testing/testing.go:1726 +0xa85
main.main()
	_testmain.go:203 +0x3bd

goroutine 92 [sync.Cond.Wait, 9 minutes]:
sync.runtime_notifyListWait(0xc0000cfa50, 0x0)
	C:/Program Files/Go/src/runtime/sema.go:517 +0x152
sync.(*Cond).Wait(0xc0000cfa40)
	C:/Program Files/Go/src/sync/cond.go:70 +0xa5
github.com/influxdata/telegraf/testutil.(*Accumulator).Wait(0xc00010c070, 0x3)
	C:/Users/circleci.PACKER-633B1A5A/project/testutil/accumulator.go:332 +0x1be
github.com/influxdata/telegraf/plugins/inputs/statsd.TestCachesExpireAfterMaxTTL(0xc000065d40?)
	C:/Users/circleci.PACKER-633B1A5A/project/plugins/inputs/statsd/statsd_test.go:1051 +0x67a
testing.tRunner(0xc000065d40, 0xce0a58)
	C:/Program Files/Go/src/testing/testing.go:1446 +0x217
created by testing.(*T).Run
	C:/Program Files/Go/src/testing/testing.go:1493 +0x75e

System info

master

Docker

No response

Steps to reproduce

  1. Run windows tests on CircleCI

Expected behavior

This test to pass

Actual behavior

Test fails inconsistently

Additional info

No response

@powersj powersj added the bug unexpected problem or unintended behavior label Dec 6, 2022
@powersj powersj self-assigned this Dec 6, 2022
@powersj powersj changed the title test: google_cloud_storage test: statsd.TestCachesExpireAfterMaxTTL Dec 7, 2022
@powersj powersj changed the title test: statsd.TestCachesExpireAfterMaxTTL test: statsd.TestCachesExpireAfterMaxTTL timed out Dec 7, 2022
powersj added a commit to powersj/telegraf that referenced this issue Dec 7, 2022
This test waits for 3 metrics to appear. On Windows, in CircleCI this
test has become flaky and timing out after 10mins waiting for those
metrics to show up. My hunch is that the microsecond sleep and
expiration are too short and small even when the Windows machines tend
to be very slow.

fixes: influxdata#12341
@powersj
Copy link
Contributor Author

powersj commented Dec 7, 2022

next steps: re-run PR on CI to see if error no longer reproduces

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