all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: 48024@debbugs.gnu.org
Subject: bug#48024: glib-2.62.6 build fails i686
Date: Thu, 6 May 2021 09:45:00 +0300	[thread overview]
Message-ID: <YJOQbHrljFx9KRbX@3900XT> (raw)
In-Reply-To: <87v97wj319.fsf@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]

On Wed, May 05, 2021 at 05:15:14PM -0400, Bone Baboon wrote:
> Efraim Flashner writes:
> > I looked closer at the bug report and I see they are timing out at 60
> > and 180 for Bone Baboon as they currently are.
> >
> > Bone Baboon: Can you build the attached test-glib.scm file and send back
> > the build log? I want to make sure I change the timeout to something
> > long enough.
> >
> > You can build it with 'guix build -f test-glib.scm'
> 
> I ran `guix build --file=test-glib.scm` and I was successful.

That was the plan. I bumped the test timeouts to high enough numbers so
that I could see how long it took.

> I was having trouble finding the build log.
> 
> I have instead attached the output of the build command.

It's perfect.

It looks like the two slowest are
 83/259 glib:glib / 1bit-mutex                  OK      85.13 s
 84/259 glib:glib+slow / 1bit-emufutex          OK      89.22 s

I was thinking of just tripling the duration but test_timeout_slow would
likely have been missed since it was moved from 120 to 180, and
extracting the number so I could multiply it by 3 isn't really the most
readable and could leave the timeout near the edge. I've gone ahead and
multiplied it by 10, if a test would hang forever it's still killed and if
there's high load on a slow machine it should still pass.



-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-05-06  6:46 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
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 [this message]
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=YJOQbHrljFx9KRbX@3900XT \
    --to=efraim@flashner.co.il \
    --cc=48024@debbugs.gnu.org \
    --cc=bone.baboon@disroot.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.