From: Ricardo Wurmus <rekado@elephly.net>
To: Ben Sturmfels <ben@sturm.com.au>
Cc: 26647@debbugs.gnu.org
Subject: bug#26647: Upgrade fabric to 1.13.2, remove upstreamed patch.
Date: Tue, 25 Apr 2017 15:18:41 +0200 [thread overview]
Message-ID: <871ssgsk0e.fsf@elephly.net> (raw)
In-Reply-To: <87fugxky57.fsf@sturm.com.au>
Hi Ben,
> The attached patch upgrades fabric from 1.13.1 to 1.13.2. The new
> upstream version incorporates the patch that was previously required for
> tests to pass. Yay!
I have tried your patch but the tests seem to time out at this point:
Alias expansion ... ok
test_tasks.TestExecute.test_calls_task_function_objects
should execute the passed-in function object ... ok
test_tasks.TestExecute.test_nested_execution_with_explicit_ports
nested executions should work with defined ports
*crickets*
After about an hour I aborted the build. Is this test supposed to take
a very long time?
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-04-25 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 2:40 bug#26647: Upgrade fabric to 1.13.2, remove upstreamed patch Ben Sturmfels
2017-04-25 13:18 ` Ricardo Wurmus [this message]
2017-04-26 0:26 ` Ben Sturmfels
2017-09-01 22:48 ` [bug#26647] " Ludovic Courtès
2017-09-06 0:54 ` Ben Sturmfels
2017-11-07 12:54 ` Ben Sturmfels
2017-11-07 13:21 ` Ben Sturmfels
2017-11-07 13:24 ` Ben Sturmfels
2017-11-07 13:46 ` Ricardo Wurmus
2017-12-02 0:06 ` Ben Sturmfels
2018-06-10 5:18 ` bug#26647: " 宋文武
2018-06-12 2:14 ` [bug#26647] " Ben Sturmfels
2018-06-12 11:51 ` bug#26647: " 宋文武
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=871ssgsk0e.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=26647@debbugs.gnu.org \
--cc=ben@sturm.com.au \
/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).