-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Bug report for failed CircleCI build (job: loadtest-with-github-reports) #5233
Comments
Link to latest failed build: https://circleci.com/gh/open-telemetry/opentelemetry-collector-contrib/160583 Test Failures
|
Link to latest failed build: https://circleci.com/gh/open-telemetry/opentelemetry-collector-contrib/160589 Test Failures
|
Link to latest failed build: https://circleci.com/gh/open-telemetry/opentelemetry-collector-contrib/160781 Test Failures
|
Test Failure in file TestIdleMode is fixed already, as the expected performance value of CPU has been increased. Test Failures for TestLog10kDPS/OTLP-HTTP and TestMetric10kDPS/SignalFx are also fixed with other commits by increasing the expected RAM limit. |
…etry#5233) Split `pmetric.MetricValueType` into `NumberDataPointValueType` and `ExemplarValueType` 1. `NumberDataPoint.ValueType()` now returns a `NumberDataPointValueType` that can be `NumberDataPointValueTypeInt` or `NumberDataPointValueTypeDouble`. 2. `pmetric.Exemplar.ValueType()` now returns a `ExemplarValueType` that can be `ExemplarValueInt` or `ExemplarValueDouble`. 1 Use case is the most common. Thats why we are keeping backward compatibility for it. 2 is rarely being used. So we don't keep backward compatibility for it to avoid mixing the split types. Co-authored-by: Alex Boten <[email protected]>
Auto-generated report for
loadtest-with-github-reports
job build.Link to failed build: https://circleci.com/gh/open-telemetry/opentelemetry-collector-contrib/160549
Test Failures
Note: Information about any subsequent build failures that happen while
this issue is open, will be added as comments with more information to this issue.
The text was updated successfully, but these errors were encountered: