From: Vagrant Cascadian <vagrant@debian.org>
To: Julien Lepiller <julien@lepiller.eu>, 45943@debbugs.gnu.org
Subject: bug#45943: php 7.4.14 fails tests on aarch64
Date: Mon, 18 Jan 2021 09:56:38 -0800 [thread overview]
Message-ID: <87mtx6nn6x.fsf@yucca> (raw)
In-Reply-To: <1D88A62C-89D0-4846-B1EC-CB3564399E00@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
On 2021-01-18, Julien Lepiller wrote:
> What does the log say? It should list test failures at the end.
I don't have the system handy at the moment, but there is a recent build
log failure from staging:
https://ci.guix.gnu.org/build/187255/log/raw
It appears to have logged 6 failures, though I haven't managed to find
which tests failed in the build output at a cursory glance...
Will try to get a failed build log locally when I get a chance to more
easily debug and review...
live well,
vagrant
> Le 17 janvier 2021 15:56:34 GMT-05:00, Vagrant Cascadian <vagrant@debian.org> a écrit :
>>php 7.4.14 fails to build on aarch64 due to test suite failures.
>>
>>Reverting back to php 7.4.13 by reverting commit
>>d033540e6c113323089403a26e39f9a288c9c857 works fine for me, though
>>obviously it would be better to track down the exact test suite failure
>>and figure out a proper fix.
>>
>>This blocks numerous other packages from building, such as libsoup,
>>which blocks building of network-manager.
>>
>>
>>live well,
>> vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-01-18 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 20:56 bug#45943: php 7.4.14 fails tests on aarch64 Vagrant Cascadian
2021-01-18 12:14 ` Julien Lepiller
2021-01-18 17:56 ` Vagrant Cascadian [this message]
2021-01-23 0:14 ` Vagrant Cascadian
2023-07-20 19:49 ` Vagrant Cascadian
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=87mtx6nn6x.fsf@yucca \
--to=vagrant@debian.org \
--cc=45943@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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).