You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[C++] Valgrind fails consistently on Azure tests #47485
The above PR updates xxhash and fixes the build issue but the job still fails due to an azure test failing. The issue is unrelated to the previous one so we should fix it. Full log on the link
==17355== LEAK SUMMARY:
==17355== definitely lost: 1,856 bytes in 8 blocks
==17355== indirectly lost: 78,096 bytes in 40 blocks
==17355== possibly lost: 0 bytes in 0 blocks
==17355== still reachable: 9,874 bytes in 157 blocks
==17355== suppressed: 0 bytes in 0 blocks
==17355== Reachable blocks (those to which a pointer was found) are not shown.
==17355== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==17355==
==17355== For lists of detected and suppressed errors, rerun with: -s
==17355== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
Activity
pitrou commentedon Sep 3, 2025
I've opened Azure/azure-sdk-for-cpp#6722 upstream. I'm not sure that is actually the issue, but still worth reporting.
pitrou commentedon Sep 3, 2025
Ok, after some gdb-based investigation, it does seem like a bug in the Azure SDK.
apacheGH-47485: [C++][CI] Work around Valgrind failure on Azure tests
GH-47485: [C++][CI] Work around Valgrind failure on Azure tests (#47496)
pitrou commentedon Sep 4, 2025
Issue resolved by pull request 47496
#47496
apacheGH-47485: [C++][CI] Work around Valgrind failure on Azure tests (…
apacheGH-47485: [C++][CI] Work around Valgrind failure on Azure tests (…