GH-43808: [C++] skip -0117 in StrptimeZoneOffset for old glibc#44621
GH-43808: [C++] skip -0117 in StrptimeZoneOffset for old glibc#44621kou merged 3 commits intoapache:mainfrom
-0117 in StrptimeZoneOffset for old glibc#44621Conversation
|
|
|
|
|
Hmm. It seems that we need to improve the added condition... Java JNI / AMD64 manylinux2014 Java JNI: https://github.com/apache/arrow/actions/runs/11692780048/job/32562887155?pr=44621#step:7:3448 C++ / AMD64 Conda C++ AVX2: https://github.com/apache/arrow/actions/runs/11692780055/job/32562895558?pr=44621#step:7:4505 |
Or just the test expectations need to depend on |
|
FWIW, I don't mind how this is done. We could also add #if defined(__GLIBC__) && defined(__GLIBC_MINOR__) && (__GLIBC__ == 2) && (__GLIBC_MINOR__ < 28)in arrow/cpp/src/arrow/util/value_parsing_test.cc Lines 829 to 832 in 11c11a4 directly, but the reason I went with this is that my understanding is that it's unlike that old glibc actually supports this feature, and we might as well reflect that...? |
|
I think that the test failure shows that glibc used by these CI supports |
-0117 in StrptimeZoneOffset for old glibc
|
|
You're right, that existing skip was a red herring. I think the only issue is with the |
a3f3105 to
5ce5c5d
Compare
|
Gentle ping @kou |
|
The AMD64 Windows MinGW CLANG64 C++ job has just started failing but it does not seem related to the changes on the PR. |
|
It's unrelated. I've opened a new issue for it: #44730 |
|
@h-vetinari Could you update the PR description before we merge this? |
Done |
|
|
|
|
|
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 3f25672. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 49 possible false positives for unstable benchmarks that are known to sometimes produce them. |
Rationale for this change
Enable tests for libarrow in conda-forge: #35587
What changes are included in this PR?
old glibc does not actually support timezones like
-0117(used inStrptimeZoneOffsettest). The exact lower bound for glibc is hard for me to determine; I know that it passes with 2.28 and that it fails with 2.17. Anything in between is an open question. I went with the conservative option here.Are these changes tested?
Tested in conda-forge/arrow-cpp-feedstock#1058
Are there any user-facing changes?
TimestampParser.StrptimeZoneOffsetwith old glibc #43808