all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 67829@debbugs.gnu.org
Cc: John Kehayias <john.kehayias@protonmail.com>
Subject: bug#67829: qtwebengine new failure on i686
Date: Thu, 14 Dec 2023 15:33:49 -0500	[thread overview]
Message-ID: <8734w48qxe.fsf@gmail.com> (raw)

Hello,

qtwebengine was marked as newly failing by Cuirass on Berlin, as a
result to the xorg-server update in
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=8083c7abbf3a346162fcc4b8d5aa50555c0f3179.

--8<---------------cut here---------------start------------->8---
v8_use_external_startup_data=false
CMake Error at /tmp/guix-build-qtwebengine-6.5.2.drv-0/qtwebengine-everywhere-src-6.5.2/cmake/Gn.cmake:75 (message):
  

  -- GN FAILED

  ERROR at //BUILD.gn:1652:1: Assertion failed.

  assert(

  ^-----

  'target_cpu=x86' is not supported for 'target_os=linux'.  Consider omitting
  'target_cpu' (default) or using 'target_cpu=x64' instead.

  See //BUILD.gn:1653:5:

      is_valid_x86_target || target_cpu != "x86" || v8_target_cpu == "arm",
      ^-------------------------------------------------------------------

  This is where it was set.

  1

ninja: build stopped: subcommand failed.
--8<---------------cut here---------------end--------------->8---

I don't see how the two would be related, but I've CC'd John in case
they'd have some hunch.

Perhaps some non-deterministic issue with the 'gn' build system?  It had
succeeded here: https://ci.guix.gnu.org/build/2803939/details about a
week ago.

-- 
Thanks,
Maxim




             reply	other threads:[~2023-12-14 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 20:33 Maxim Cournoyer [this message]
2023-12-15  6:04 ` bug#67829: qtwebengine new failure on i686 John Kehayias via Bug reports for GNU Guix
2023-12-16 17:34   ` Efraim Flashner
2023-12-19 16:46     ` Maxim Cournoyer

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=8734w48qxe.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=67829@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.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 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.