From: Mark H Weaver <mhw@netris.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 48024@debbugs.gnu.org
Subject: bug#48024: glib-2.62.6 build fails i686
Date: Tue, 04 May 2021 16:01:54 -0400 [thread overview]
Message-ID: <874kfinu7m.fsf@netris.org> (raw)
In-Reply-To: <YJDnPqOFdCgf+f/d@3900XT>
Hi Efraim,
Efraim Flashner <efraim@flashner.co.il> writes:
> In glib-2.68 test_timeout and test_timeout_slow are set to 60 and 180
> respectively.
Right. Unfortunately, these timeouts are too short for many slower
machines, such as 32-bit ARM systems. Bone Baboon has also recently
reported being unable to build 'glib' on a 32-bit i686 system due to
these timeouts, even when making extreme efforts to reduce load from
other processes.
> As I understand it, the tests which are are tagged '+slow' get the
> test_timeout_slow property, with the test taking the longest on that
> machine was glib:glib+slow / gvariant, at 65 seconds. By comparison, on
> my Ryzen 3900XT machine it took 2.58 seconds. I figured even at double
> that time it still fell within the 180 seconds given by default in the
> test suite so it was likely safe to remove the substitution entirely.
I think that this recently-reported bug (<https://bugs.gnu.org/48024>)
demonstrates that we can't safely remove the substitution.
> I don't have other suitably slow hardware to test on, but I am building
> it on my aarch64 board too, so I should be able to say in a day or two
> if it works there.
I don't see how a build test on your aarch64 board is relevant here.
As the comment above the 'increase-test-timeout' phase indicated, the
timeouts were increased for the sake of slower 32-bit ARM boards.
I think that we should re-introduce the 'increase-test-timeout' phase
for all systems on the 'core-updates' branch. Is there a disadvantage,
besides having to wait a couple more minutes if a test fails to
terminate?
What do you think?
Regards,
Mark
--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>.
next prev parent reply other threads:[~2021-05-04 20:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 3:35 bug#48024: glib-2.62.6 build fails i686 Bone Baboon via Bug reports for GNU Guix
2021-04-26 15:26 ` raingloom
2021-04-27 19:25 ` Bone Baboon via Bug reports for GNU Guix
2021-04-28 3:23 ` Mark H Weaver
2021-05-03 22:00 ` Bone Baboon via Bug reports for GNU Guix
2021-05-04 0:38 ` Leo Famulari
2021-05-04 3:01 ` Mark H Weaver
2021-05-04 6:18 ` Efraim Flashner
2021-05-04 20:01 ` Mark H Weaver [this message]
2021-05-04 20:08 ` Mark H Weaver
2021-05-04 22:52 ` Bone Baboon via Bug reports for GNU Guix
2021-05-05 8:38 ` Efraim Flashner
2021-05-05 21:15 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06 0:20 ` Mark H Weaver
2021-05-06 0:35 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06 6:45 ` Efraim Flashner
2021-05-06 9:06 ` Bengt Richter
2021-05-06 17:44 ` Bone Baboon via Bug reports for GNU Guix
2021-05-07 17:46 ` Mark H Weaver
2021-05-08 13:26 ` Bengt Richter
2022-03-18 2:26 ` Maxim Cournoyer
2021-05-04 3:56 ` Mark H Weaver
2021-05-05 16:34 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06 8:46 ` Mark H Weaver
2021-05-06 19:36 ` Bone Baboon via Bug reports for GNU Guix
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=874kfinu7m.fsf@netris.org \
--to=mhw@netris.org \
--cc=48024@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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.