Tracer.WithActiveSpan RedHat Entreprise Linux 9.4

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)

The failure is in sdk/test/trace/tracer_test.cc at lines 1075-1076, in Tracer.WithActiveSpan; start by running that GoogleTest case and comparing the reported parent and trace IDs. Reproduce it on Red Hat Enterprise Linux 9.4, then trace the implementation used by the test to determine why its expectations differ. Completion requires identifying the cause and documenting the appropriate resolution.