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

trace.FastRandomNumberGeneratorTest.GenerateUniqueNumbers fails for alpine linux #3062

Open
svrnm opened this issue Sep 13, 2024 · 4 comments
Labels
bug Something isn't working needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. Stale triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@svrnm
Copy link
Member

svrnm commented Sep 13, 2024

Describe your environment

Alpine Linux Edge, on different architectures (see below)

Steps to reproduce

I tried to update the alpine packages for opentelemetry-cpp from 1.11 to 1.16, unfortunately I get this issue with all supported platforms:

https://gitlab.alpinelinux.org/svrnm/aports/-/pipelines/258676

/builds/svrnm/aports/testing/opentelemetry-cpp/src/opentelemetry-cpp-1.16.1/sdk/test/common/fast_random_number_generator_test.cc:20: Failure
Value of: values.insert(random_number_generator()).second
  Actual: false
Expected: true

To reproduce I have the following code prepared, and I was able to reproduce the issue locally

https://github.com/svrnm/otel-abuild

What is the expected behavior?

The test should succeed.

What is the actual behavior?

Te thest is failing.

Additional context

I tried to fix the issue myself, I have a few findings but none of them helped me to find a final solution:

  • The issue shows up when GCC14 is used (in alpine edge), but does not show up with GCC13 (with alpine non-edge)
  • When I add some code to output the number in the test.cc file it's always 0
@svrnm svrnm added the bug Something isn't working label Sep 13, 2024
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 13, 2024
@marcalff marcalff added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 23, 2024
Copy link

This issue was marked as stale due to lack of activity.

@github-actions github-actions bot added the Stale label Nov 23, 2024
@svrnm
Copy link
Member Author

svrnm commented Jan 10, 2025

I will close this now and see if I can get it work with a more recent version, will reopen if necessary

@svrnm svrnm closed this as completed Jan 10, 2025
@strophy
Copy link

strophy commented Feb 12, 2025

@svrnm I just hit this same error trying to build v1.19.0 on Alpine 3.21 x86_64, seems like it's still an issue

@svrnm svrnm reopened this Feb 25, 2025
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 25, 2025
@svrnm
Copy link
Member Author

svrnm commented Feb 25, 2025

@open-telemetry/cpp-maintainers FYI, this still is an issue with 1.19 on most recent alpine builds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. Stale triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants