From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>, 49368@debbugs.gnu.org
Subject: bug#49368: Guile 3.0.7 test failures on i686-linux, glibc 2.33 [core-updates]
Date: Sun, 04 Jul 2021 14:31:54 +0200 [thread overview]
Message-ID: <707865c726394c527a9141e742a575c2e4e19a67.camel@telenet.be> (raw)
In-Reply-To: <87tulbxegp.fsf@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
Ludovic Courtès schreef op za 03-07-2021 om 23:41 [+0200]:
> On current ‘core-updates’
> (ca. 39f1486efd70712416ca784f9014132644b04155), Guile 3.0.7,
> specifically (@@ (gnu packages commencement) guile-final) fails tests on
> i686-linux:
>
> --8<---------------cut here---------------start------------->8---
> Running numbers.test
> FAIL: numbers.test: Number-theoretic division: euclidean/: mixed types: (130.0 10/7)
> [...]
Curiously, on core-updates, ceiling/ is inconsistent with ceiling-quotient
and ceiling-remainder:
scheme@(guile-user) [1]> (ceiling/ 130.0 -10/7)
$28 = -90.0
$29 = 1.4285714285714257
scheme@(guile-user) [1]> (ceiling-quotient 130.0 -10/7)
$30 = -91.0
scheme@(guile-user) [1]> (ceiling-remainder 130.0 -10/7)
$31 = 0.0
But on 'master', the results are consistent:
scheme@(guile-user)> (ceiling/ 130.0 -10/7)
$1 = -91.0
$2 = 0.0
scheme@(guile-user)> (ceiling-quotient 130.0 -10/7)
$3 = -91.0
scheme@(guile-user)> (ceiling-remainder 130.0 -10/7)
$4 = 0.0
To be investigated ...
Greetings,
Maxime.
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-07-04 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 21:41 bug#49368: Guile 3.0.7 test failures on i686-linux, glibc 2.33 [core-updates] Ludovic Courtès
2021-07-04 12:06 ` Maxime Devos
2021-07-04 12:31 ` Maxime Devos [this message]
2021-07-06 13:24 ` Maxime Devos
2021-07-24 18:46 ` Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=707865c726394c527a9141e742a575c2e4e19a67.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=49368@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.