pitrou commented on PR #41163: URL: https://github.com/apache/arrow/pull/41163#issuecomment-2051322908
Ok... This seems to assume that Valgrind is buggy and doesn't handle a calloc() call correctly, while our Azure FS implementation (and/or the Azure SDK) is spotless and cannot contain any bugs. I'm quite skeptical. There are couple [search results online](https://www.google.com/search?client=firefox-b-d&q=%22xmlNewGlobalState%22+%22valgrind%22) for this, but very few, so I'm not sure it's really an issue in libxml or in the Azure SDK. Have you tried opening a bug report here? Really, deciding that errors are "false positives" without any further analysis does not strike me as a serious way to deal with CI issues. And even if we decide it's a false positive, we can add a Valgrind suppression for the case of `xmlNewGlobalState`, which would still help us find other issues: https://github.com/apache/arrow/blob/main/cpp/valgrind.supp -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
