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

Tracer.WithActiveSpan RedHat Entreprise Linux 9.4 #3188

Open
olivier-perrault-ibm opened this issue Dec 4, 2024 · 1 comment
Open

Tracer.WithActiveSpan RedHat Entreprise Linux 9.4 #3188

olivier-perrault-ibm opened this issue Dec 4, 2024 · 1 comment
Labels
bug Something isn't working triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@olivier-perrault-ibm
Copy link

olivier-perrault-ibm commented Dec 4, 2024

Problem
I am encountering a test failure with Tracer.WithActiveSpan and unsure what might be causing this. The test expects the spas trace id and the first space context trace id to mismatch. However mine match. Any ideas?

EXPECT_NE(spans.at(0).get()->GetTraceId(), span_first->GetContext().trace_id());

256/465 Test #256: trace.Tracer.WithActiveSpan ..........................................................................***Failed    0.00 sec
Running main() from /builddir/build/BUILD/googletest-release-1.11.0/googletest/src/gtest_main.cc
Note: Google Test filter = Tracer.WithActiveSpan
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Tracer
[ RUN      ] Tracer.WithActiveSpan
/home/fyreuser/repos/ace-tracing/opentelemetry-cpp/sdk/test/trace/tracer_test.cc:1075: Failure
Expected equality of these values:
  spans.at(0).get()->GetParentSpanId()
    Which is: 8-byte object <05-54 6F-11 9A-43 44-63>
  opentelemetry::trace::SpanId()
    Which is: 8-byte object <00-00 00-00 00-00 00-00>
/home/fyreuser/repos/ace-tracing/opentelemetry-cpp/sdk/test/trace/tracer_test.cc:1076: Failure
Expected: (spans.at(0).get()->GetTraceId()) != (span_first->GetContext().trace_id()), actual: 16-byte object <8E-23 D2-6D B7-9B 1E-4B 14-C8 87-1B 2D-DE CE-32> vs 16-byte object <8E-23 D2-6D B7-9B 1E-4B 14-C8 87-1B 2D-DE CE-32>
[  FAILED  ] Tracer.WithActiveSpan (0 ms)
[----------] 1 test from Tracer (0 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (0 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Tracer.WithActiveSpan

 1 FAILED TEST

Environment
RedHat Entreprise Linux 9.4
Intel Core Processor (Broadwell, IBRS)

@olivier-perrault-ibm olivier-perrault-ibm added the bug Something isn't working label Dec 4, 2024
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 4, 2024
@marcalff
Copy link
Member

marcalff commented Jan 8, 2025

Bonjour @olivier-perrault-ibm

I am very puzzled by this part of the test failure:

/home/fyreuser/repos/ace-tracing/opentelemetry-cpp/sdk/test/trace/tracer_test.cc:1076: Failure
Expected: (spans.at(0).get()->GetTraceId()) != (span_first->GetContext().trace_id()), actual: 16-byte object <8E-23 D2-6D B7-9B 1E-4B 14-C8 87-1B 2D-DE CE-32> vs 16-byte object <8E-23 D2-6D B7-9B 1E-4B 14-C8 87-1B 2D-DE CE-32>

According to this test log, the test fails because the two parts are expected to be different, and yet they are equal (and the binary bumps are identical).

In the opentelemetry-cpp source code, the line that corresponds to opentelemetry-cpp/sdk/test/trace/tracer_test.cc:1076 reads as:

    EXPECT_EQ(spans.at(0).get()->GetTraceId(), span_first->GetContext().trace_id());

This is EXPECT_EQ, which expects ... equality.

Please clarify the exact version used for opentelemetry-cpp, down to the github commit or label, and clarify if you have any local changes.

Also, please clarify if other tests are also failing and how, this will help to identify the root cause.

Thanks.

@marcalff marcalff added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

2 participants