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

Bug report for failed CircleCI build (job: loadtest-with-github-reports) #5233

Closed
opentelemetry-bot opened this issue Sep 14, 2021 · 4 comments
Labels
ci-cd CI, CD, testing, build issues good first issue Good for newcomers

Comments

@opentelemetry-bot
Copy link

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

  • TestIdleMode

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.

@opentelemetry-bot
Copy link
Author

Link to latest failed build: https://circleci.com/gh/open-telemetry/opentelemetry-collector-contrib/160583

Test Failures

  • TestMetric10kDPS
  • TestMetric10kDPS/SignalFx

@opentelemetry-bot
Copy link
Author

Link to latest failed build: https://circleci.com/gh/open-telemetry/opentelemetry-collector-contrib/160589

Test Failures

  • TestIdleMode

@opentelemetry-bot
Copy link
Author

Link to latest failed build: https://circleci.com/gh/open-telemetry/opentelemetry-collector-contrib/160781

Test Failures

  • TestLog10kDPS
  • TestLog10kDPS/OTLP-HTTP

@alolita alolita added ci-cd CI, CD, testing, build issues good first issue Good for newcomers labels Sep 30, 2021
@PaurushGarg
Copy link
Member

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.

hex1848 pushed a commit to hex1848/opentelemetry-collector-contrib that referenced this issue Jun 2, 2022
…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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-cd CI, CD, testing, build issues good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants