We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See, for example, https://app.circleci.com/pipelines/github/micrometer-metrics/micrometer/6982/workflows/66800576-a887-4030-b36a-5068d498950b/jobs/35044. JvmGcMetricsTest > gcTimingIsCorrectForPauseCycleCollectors() fails fairly often when running the zgcGenerationalTest task during the CI build. Unfortunately I think it's a matter of whether a GC happens during the test code running that is collecting numbers to make assertions about the metrics having the right numbers for GCs. I don't have a great idea how to improve this.
zgcGenerationalTest
> Task :micrometer-core:zgcGenerationalTest JvmGcMetricsTest > gcTimingIsCorrectForPauseCycleCollectors() FAILED org.opentest4j.AssertionFailedError: expected: 11L but was: 10L at app//io.micrometer.core.instrument.binder.jvm.JvmGcMetricsTest.lambda$checkPhaseCount$3(JvmGcMetricsTest.java:236)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
See, for example, https://app.circleci.com/pipelines/github/micrometer-metrics/micrometer/6982/workflows/66800576-a887-4030-b36a-5068d498950b/jobs/35044. JvmGcMetricsTest > gcTimingIsCorrectForPauseCycleCollectors() fails fairly often when running the
zgcGenerationalTest
task during the CI build. Unfortunately I think it's a matter of whether a GC happens during the test code running that is collecting numbers to make assertions about the metrics having the right numbers for GCs. I don't have a great idea how to improve this.The text was updated successfully, but these errors were encountered: