From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Ryan Sundberg <ryan@arctype.co>
Cc: 51023-done@debbugs.gnu.org
Subject: bug#51023: [PATCH] gnu: php: patch failing test case
Date: Tue, 05 Oct 2021 13:47:24 +0200 [thread overview]
Message-ID: <87pmsjr8fx.fsf@nckx> (raw)
In-Reply-To: <20211005041845.22648-1-ryan@arctype.co>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
Ryan,
Ryan Sundberg via Guix-patches via 写道:
> Fixes a failing test case in php (Zend/tests/bug74093.phpt)
> See https://github.com/php/php-src/pull/7555/files for upstream
> status.
Thanks! PHP is notorious for
sleep 4 # this is how long x took to y on my laptop in 2014
but it's the bane of many test suites (and, hence, us)…
> * gnu/local.mk: Include patch file php-bug-74093-test.patch
> * gnu/packages/patches/php-bug-74093-test.patch: Patch file
> * gnu/packages/php.scm: Add patch to php
Thanks for writing a GNU/Guix-style commit message. I made only a
few tweaks, mainly adding full stops and (section)[things].
gnu: php: Patch failing test case.
Fixes a failing test case in PHP (Zend/tests/bug74093.phpt).
See
<https://github.com/php/php-src/pull/7555/files> for upstream
status.
* gnu/packages/php.scm (php)[source]: Add patch.
* gnu/packages/patches/php-bug-74093-test.patch: New file.
* gnu/local.mk (dist_patch_DATA): Add it.
The * line order is just what I'm used to writing, nothing more.
Pushed as 9aaf402a379b9ac9e4c3eee5b16f7496d7606e91!
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2021-10-05 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 4:18 [bug#51023] [PATCH] gnu: php: patch failing test case Ryan Sundberg via Guix-patches via
2021-10-05 11:47 ` Tobias Geerinckx-Rice via Guix-patches via [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=87pmsjr8fx.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=51023-done@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=ryan@arctype.co \
/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.