-
Notifications
You must be signed in to change notification settings - Fork 29
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
Fix failing JMX tests #426
Conversation
nice findings! |
@@ -46,7 +46,7 @@ func (t *JMXTomcatJVMTestRunner) GetAgentConfigFileName() string { | |||
} | |||
|
|||
func (t *JMXTomcatJVMTestRunner) GetAgentRunDuration() time.Duration { | |||
return 2 * time.Minute | |||
return 10 * time.Minute |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is 10 minutes necessary here or can we reduce it to 5 minutes or less? or is that still too short to collect this metric. Asking since sleeping 10 minutes for a test to run slow down the testing process.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think 5 is a good balance—will make this change and keep an eye on the tests
test/metric_value_benchmark/agent_configs/jmx_tomcat_jvm_config.json
Outdated
Show resolved
Hide resolved
Run #11749486690 (integration test run from original PR)
|
Description of the issue
We have failing JMX tests throughout out integration tests for multiple OSes. Here is a failed run that shows the test failing on these metrics in a previous run—specifically the garbage collection and tomcat metrics.
Description of changes
metrics_collection_interval
to 60 seconds to better capture infrequent metrics (likejvm.gc.collections.elapsed
andjvm.gc.collections.count
)License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
I ran the integration tests in the
amazon-cloudwatch-agent
repo under the fix-JMX-integ-tests branch. That branch of the main repo is configured to run integration tests using this branch of the test repo. Here is the run: Run #11802640395