Mark Dickinson added the comment:
One more thought on the libm issues - from the logs, it looks as though the
libm implementation is coming from a fairly recent version of glibc (glibc
2.33, which was released in February 2021). There were updates to the 'exp'
implementation in glibc in
Mark Dickinson added the comment:
Here's the test_posix failure, extracted from the attachment:
==
ERROR: test_sched_rr_get_interval (test.test_posix.PosixTester)
Mark Dickinson added the comment:
Update: test_turtle is fixed (44734); I think test_math and test_cmath should
be resolved as either "third party" or "wont fix", since the issue is almost
certainly the platform libm.
That leaves test_posix, which we should probably open a fresh issue for.
Mark Dickinson added the comment:
Looks like the turtle code was changed to use `math.hypot` instead of `** 0.5`
in issue #41528. That will likely also fix the test failure, but I've opened
#44734 to fix the unnecessarily strict test.
--
___
Mark Dickinson added the comment:
The test_posix failure appears to be unrelated; I'll let others look into that
one.
The test_turtle failure looks again like a libm issue, perhaps combined with an
overeager test: we're expecting a `** 0.5` operation (which translates to a
libm pow call)
Mark Dickinson added the comment:
Extract from the log - from the configure output:
> checking for expm1... yes
and from the test output
> expm10118: expm1(27.0): expected 532048240600.79865, got 532048240600.7976
> (error = 0.00104 (17 ulps); permitted error = 0 or 5 ulps)
> expm10119:
New submission from Erich Eckner :
The following tests fails on x86 32 bit:
test_cmath test_math test_posix test_turtle - looks, like the expected
precision is too high.
Full log is attached.
--
components: Tests
files: build-log.php?a=pentium4=python
messages: 398084
nosy:
