From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 53434@debbugs.gnu.org,
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Subject: [bug#53434] Patches to unbreak many i686 packages
Date: Sun, 23 Jan 2022 22:32:36 +0100 [thread overview]
Message-ID: <87h79uyw7f.fsf_-_@gnu.org> (raw)
In-Reply-To: <34ade5841a65c40bd737fe636749d5daded44b0b.camel@telenet.be> (Maxime Devos's message of "Sat, 22 Jan 2022 20:32:37 +0100")
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> E.g., I built upower of i686-linux today, and the build log
> contained:
>
>> # UPower-DEBUG: deferring as others queued
>> # UPower-DEBUG: limiting data to last 10 seconds
>> # UPower-DEBUG: length of array (before) 3
>> # UPower-DEBUG: limiting data to last 10 seconds
>> # UPower-DEBUG: length of array (before) 3
>> # UPower-DEBUG: Using a x division of 2.000000
>> (first=1642875457,last=1642875453)
>> # UPower-DEBUG: length of array (after) 3
>> **
>> UPower:ERROR:up-self-test.c:218:up_test_history_func: assertion
>> failed (array->len == 2): (3 == 2)
>> Bail out! UPower:ERROR:up-self-test.c:218:up_test_history_func:
>> assertion failed (array->len == 2): (3 == 2)
>> FAIL up-self-test (exit status: 134)
>
>
> 1642875457 > 1642875453, so first > last, which is suspect.
>
> Would this be a 32-bit/64-bit issue?
>
> (expt 2 32) is 4294967296 which is as long as 1642875457 and
> 1642875453, so this seems like an overflow issue, so maybe?
> To be investigated ... (I'll look at the source code later).
I remember investigating it while on ‘core-updates-frozen’… and
eventually forgetting about it. :-/
I think the pragmatic approach in such situations is to:
1. Report the test failure upstream, including the test log;
2. Skip tests (ideally selectively) for i686-linux, adding a link to
the upstream bug report.
That makes sure we move forward while not just sweeping issues under the
carpet.
Ludo’.
next prev parent reply other threads:[~2022-01-23 21:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 2:54 [bug#53434] Patches to unbreak many i686 packages Denis 'GNUtoo' Carikli
2022-01-22 2:59 ` [bug#53434] [PATCH 01/11] gnu: gtk-vnc: Remove dependency on GJS on non-x86_64 Denis 'GNUtoo' Carikli
2022-01-22 2:59 ` [bug#53434] [PATCH 02/11] gnu: gtk-vnc: Build with correct librsvg Denis 'GNUtoo' Carikli
2022-01-22 2:59 ` [bug#53434] [PATCH 03/11] gnu: gnome-settings-daemon: " Denis 'GNUtoo' Carikli
2022-01-22 2:59 ` [bug#53434] [PATCH 04/11] gnu: vlc: " Denis 'GNUtoo' Carikli
2022-01-22 2:59 ` [bug#53434] [PATCH 05/11] gnu: python-dbusmock: Disable tests on i686 Denis 'GNUtoo' Carikli
2022-01-22 2:59 ` [bug#53434] [PATCH 06/11] gnu: node: " Denis 'GNUtoo' Carikli
2022-01-22 2:59 ` [bug#53434] [PATCH 07/11] gnu: guix: " Denis 'GNUtoo' Carikli
2022-01-23 21:35 ` [bug#53434] Patches to unbreak many i686 packages Ludovic Courtès
2022-01-22 2:59 ` [bug#53434] [PATCH 08/11] gnu: mesa: Disable tests on i686 Denis 'GNUtoo' Carikli
2022-01-26 3:27 ` Denis 'GNUtoo' Carikli
2022-01-22 2:59 ` [bug#53434] [PATCH 09/11] gnu: imath: " Denis 'GNUtoo' Carikli
2022-01-26 1:06 ` Denis 'GNUtoo' Carikli
2022-01-26 3:17 ` Leo Famulari
2022-01-26 3:44 ` Leo Famulari
2022-01-22 2:59 ` [bug#53434] [PATCH 10/11] gnu: openexr: " Denis 'GNUtoo' Carikli
2022-01-22 2:59 ` [bug#53434] [PATCH 11/11] gnu: upower: " Denis 'GNUtoo' Carikli
2022-01-24 10:43 ` Maxime Devos
2022-02-16 13:53 ` [bug#53434] Patches to unbreak many i686 packages Ludovic Courtès
2022-02-16 16:38 ` Maxime Devos
2022-02-17 10:40 ` Ludovic Courtès
2022-02-17 20:30 ` Maxime Devos
2022-02-18 7:50 ` Maxime Devos
2022-02-18 13:43 ` Ludovic Courtès
2022-04-23 19:54 ` Denis 'GNUtoo' Carikli
2022-04-28 21:35 ` bug#53434: " Ludovic Courtès
2022-01-22 12:38 ` [bug#53434] " Maxime Devos
2022-01-22 16:49 ` Denis 'GNUtoo' Carikli
2022-01-22 19:19 ` Denis 'GNUtoo' Carikli
2022-01-22 19:32 ` Maxime Devos
2022-01-23 21:32 ` Ludovic Courtès [this message]
2022-01-22 19:34 ` Maxime Devos
2022-01-23 22:39 ` Ludovic Courtès
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=87h79uyw7f.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=53434@debbugs.gnu.org \
--cc=GNUtoo@cyberdimension.org \
--cc=maximedevos@telenet.be \
/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.