From: Marius Bakke <mbakke@fastmail.com>
To: Bradley Haggerty <bradigger@gmail.com>, 37682@debbugs.gnu.org
Subject: bug#37682: weston 6.0.1 build failure
Date: Thu, 24 Oct 2019 20:46:38 +0200 [thread overview]
Message-ID: <87k18uugkx.fsf@devup.no> (raw)
In-Reply-To: <CABGw91eUW4JsJwrLkQ--5qdfbAZRk6qLAnDM+u4oL8Yg1UwsVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
Bradley Haggerty <bradigger@gmail.com> writes:
> guix 525ef21
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 525ef21ba0d4a50a7d21f5543db40b6cc328f9cd
>
> builder for `/gnu/store/i1k1znpbswllwhaja6g3nlbb4g2gpk1c-weston-6.0.1.drv'
> failed with exit code 1
> build of /gnu/store/i1k1znpbswllwhaja6g3nlbb4g2gpk1c-weston-6.0.1.drv failed
> View build log at
> '/var/log/guix/drvs/i1/k1znpbswllwhaja6g3nlbb4g2gpk1c-weston-6.0.1.drv.bz2'.
> guix package: error: build of
> `/gnu/store/i1k1znpbswllwhaja6g3nlbb4g2gpk1c-weston-6.0.1.drv' failed
>
> build log: https://paste.debian.net/1105575/
So apparently this only happens on some systems. I can not reproduce it
on my dinky laptop, but I can on a Haswell Xeon server.
Can you file a bug report about this upstream at
<https://gitlab.freedesktop.org/wayland/weston>?
We can probably disable the test in question, but it would be good to
have an upstream bug report to link to.
On the Guix CI, Weston builds successfully only on armhf:
https://ci.guix.gnu.org/search?query=weston
It is possible that clocking down your CPU while running the tests would
help as a band-aid...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-10-24 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 16:35 bug#37682: weston 6.0.1 build failure Bradley Haggerty
2019-10-24 18:46 ` Marius Bakke [this message]
2019-10-24 20:29 ` Gábor Boskovits
2019-10-25 11:11 ` Gábor Boskovits
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k18uugkx.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=37682@debbugs.gnu.org \
--cc=bradigger@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).