From: Rutger Helling <rhelling@mykolab.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 31982@debbugs.gnu.org
Subject: bug#31982: shaderc fails its test suite on all hydra-supported systems
Date: Wed, 27 Jun 2018 11:07:38 +0200 [thread overview]
Message-ID: <20180627110738.33ff76d7@mykolab.com> (raw)
In-Reply-To: <87zhzhbdag.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
Hi Mark,
unfortunately I don't really have the time to look at it in-depth now.
I've disabled the tests for now so I'm not blocking you. I'll take
another look at the tests after you've fixed 'meson-build-system.
On Tue, 26 Jun 2018 14:41:59 -0400
Mark H Weaver <mhw@netris.org> wrote:
> Hi Rutger,
>
> In commit 7f540654873a2761746bdc43be4727cad99b92c0, you updated
> 'sharerc' to upstream commit be8e087 and enabled tests.
>
> It turns out that it fails its test suite on all systems supported by
> Hydra, but the failure is effectively being ignored, because of
> <https://bugs.gnu.org/31974>.
>
> I'd like to fix 'meson-build-system' to always return #t from phases
> and to report errors using exceptions, which would effectively work
> around the aforementioned bug, but then that would cause 'shaderc' to
> start failing in earnest.
>
> See <https://bugs.gnu.org/31982> for more details.
>
> Would you be willing to take a look and fix 'sharerc' so that it won't
> start failing when I fix 'meson-build-system'?
>
> Regards,
> Mark
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-06-27 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 17:44 bug#31982: shaderc fails its test suite on all hydra-supported systems Mark H Weaver
2018-06-26 18:41 ` Mark H Weaver
2018-06-27 9:07 ` Rutger Helling [this message]
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=20180627110738.33ff76d7@mykolab.com \
--to=rhelling@mykolab.com \
--cc=31982@debbugs.gnu.org \
--cc=mhw@netris.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.