<!DOCTYPE html>
<html data-lt-installed="true">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body style="padding-bottom: 1px;">
<p>Hi, Sergey,</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 20.12.2024 15:15, Sergey Kaplun
wrote:<br>
</div>
<blockquote type="cite" cite="mid:Z2Vf7LQ6SYHPmYYL@root">
<pre class="moz-quote-pre" wrap="">Hi, Sergey!
Thanks for the review!
See my answers below.
On 20.12.24, Sergey Bronnikov wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hello, Sergey,
thanks for the patch! See comments below.
On 19.12.2024 12:30, Sergey Kaplun wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">The `strtod parsing` subtest in the <lib/base/tonumber_scan.lua> checks
the results yielded by the `strtod()` via FFI call. In glibc versions
before 2.28 it returns an incorrect result (NaN instead of inf) for
"0x3p1023" [1]. This patch hardens the skipcond for this test for a
smaller version of the libc installed.
[1]:<a class="moz-txt-link-freetext" href="https://sourceware.org/bugzilla/show_bug.cgi?id=23279">https://sourceware.org/bugzilla/show_bug.cgi?id=23279</a>
---
Branch:<a class="moz-txt-link-freetext" href="https://github.com/tarantool/luajit/tree/skaplun/gh-noticket-fix-glibc-versions">https://github.com/tarantool/luajit/tree/skaplun/gh-noticket-fix-glibc-versions</a>
The CI failure for libc 2.23 (ubuntu 16):
<a class="moz-txt-link-freetext" href="https://github.com/tarantool/tarantool/actions/runs/12376159316/job/34542626889?pr=10949#step:5:13916">https://github.com/tarantool/tarantool/actions/runs/12376159316/job/34542626889?pr=10949#step:5:13916</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Ubuntu 16.04 EOL and EOS are reached [1]
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">The CI failure for libc 2.24 (debian 9):
<a class="moz-txt-link-freetext" href="https://github.com/tarantool/tarantool/actions/runs/12376159307/job/34542633454?pr=10949#step:5:13859">https://github.com/tarantool/tarantool/actions/runs/12376159307/job/34542633454?pr=10949#step:5:13859</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Debian 9 EOL is reached 4 years ago [2]
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">The CI failure for libc 2.27 (ubuntu 18):
<a class="moz-txt-link-freetext" href="https://github.com/tarantool/tarantool/actions/runs/12376159278/job/34542625496?pr=10949#step:5:11743">https://github.com/tarantool/tarantool/actions/runs/12376159278/job/34542625496?pr=10949#step:5:11743</a>
The CI pass for libc 2.31 (ubuntu 20):
<a class="moz-txt-link-freetext" href="https://github.com/tarantool/tarantool/actions/runs/12376159289/job/34542630993?pr=10949">https://github.com/tarantool/tarantool/actions/runs/12376159289/job/34542630993?pr=10949</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Ubuntu 20.04 support ends in 3 months and 2 week [1].
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Yes, unfortunately we should keep (AFAICS) these runners to check the
installations for our customers.
</pre>
</blockquote>
<p>I believe we will clarify a list of Linux distros in a separate
activity.</p>
<p><br>
</p>
<blockquote type="cite" cite="mid:Z2Vf7LQ6SYHPmYYL@root">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
test/LuaJIT-tests/lib/base/tonumber_scan.lua | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/test/LuaJIT-tests/lib/base/tonumber_scan.lua b/test/LuaJIT-tests/lib/base/tonumber_scan.lua
index ac7d68a4..800c57b0 100644
--- a/test/LuaJIT-tests/lib/base/tonumber_scan.lua
+++ b/test/LuaJIT-tests/lib/base/tonumber_scan.lua
@@ -186,9 +186,11 @@ do --- tonumber parsing
test_conv(tonumber)
end
--- Skip for the old libc version with the bug in the `strtod()`.
--- See alsohttps://sourceware.org/bugzilla/show_bug.cgi?id=16151.
-do --- strtod parsing -libc<2.19
+-- Skip for the old libc version with the bugs in the `strtod()`.
+-- Affected versions:
+-- * <2.19:<a class="moz-txt-link-freetext" href="https://sourceware.org/bugzilla/show_bug.cgi?id=16151">https://sourceware.org/bugzilla/show_bug.cgi?id=16151</a>.
+-- * <2.28:<a class="moz-txt-link-freetext" href="https://sourceware.org/bugzilla/show_bug.cgi?id=23279">https://sourceware.org/bugzilla/show_bug.cgi?id=23279</a>.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I propose to skip strtod test when Glibc is older than say 2.30 [3] and
avoid testing
with ancient Glibc versions because Glibc implementation is buggy [4] and
a there are lot of bugs in old and more or less new versions:
v2.41 [5], v2.22 [6], v2.27 [7], v2.15 [8], v2.33 [9] etc [10].
I don't think we should waste our time with issues like this.
1. <a class="moz-txt-link-freetext" href="https://endoflife.date/ubuntu">https://endoflife.date/ubuntu</a>
2. <a class="moz-txt-link-freetext" href="https://endoflife.date/debian">https://endoflife.date/debian</a>
3. <a class="moz-txt-link-freetext" href="https://sourceware.org/glibc/wiki/Release">https://sourceware.org/glibc/wiki/Release</a>
4.
<a class="moz-txt-link-freetext" href="https://github.com/tarantool/luajit/blob/cd5ab5da9b56bf560407554c0377cfa8567d4430/src/lj_strscan.c#L20-L27">https://github.com/tarantool/luajit/blob/cd5ab5da9b56bf560407554c0377cfa8567d4430/src/lj_strscan.c#L20-L27</a>
5. <a class="moz-txt-link-freetext" href="https://sourceware.org/bugzilla/show_bug.cgi?id=30220">https://sourceware.org/bugzilla/show_bug.cgi?id=30220</a>
6. <a class="moz-txt-link-freetext" href="https://sourceware.org/bugzilla/show_bug.cgi?id=19380">https://sourceware.org/bugzilla/show_bug.cgi?id=19380</a>
7. <a class="moz-txt-link-freetext" href="https://sourceware.org/bugzilla/show_bug.cgi?id=15744">https://sourceware.org/bugzilla/show_bug.cgi?id=15744</a>
8. <a class="moz-txt-link-freetext" href="https://sourceware.org/bugzilla/show_bug.cgi?id=14049">https://sourceware.org/bugzilla/show_bug.cgi?id=14049</a>
9. <a class="moz-txt-link-freetext" href="https://sourceware.org/bugzilla/show_bug.cgi?id=26137">https://sourceware.org/bugzilla/show_bug.cgi?id=26137</a>
10.
<a class="moz-txt-link-freetext" href="https://sourceware.org/bugzilla/buglist.cgi?bug_status=__all__&content=strtod&no_redirect=1&order=bug_id%20DESC&product=glibc&query_format=specific">https://sourceware.org/bugzilla/buglist.cgi?bug_status=__all__&content=strtod&no_redirect=1&order=bug_id%20DESC&product=glibc&query_format=specific</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Yes, I agree that this should be the last red line for us. If the test
will fail again due to glibc, it will be easier just to drop it. For
now, I see no failures for versions 2.31 -- 2.40, and find no bugs
related to our tests that affected versions 2.28 -- 2.30, so let's skip
it for versions less than 2.28 for now.</pre>
</blockquote>
<p>Okay, LGTM then.</p>
<p>Also discussed it and decided to remove the test if the same
issue will happen next time.<br>
</p>
<blockquote type="cite" cite="mid:Z2Vf7LQ6SYHPmYYL@root">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">+do --- strtod parsing -libc<2.28
test_conv(function(s)
local d = ffi.C.strtod(s, e)
return (e[0][0] == 0 and #s ~= 0) and d or nil
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
</body>
<lt-container></lt-container>
</html>