From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 30524@debbugs.gnu.org
Subject: bug#30524: [PATCH] gnu: java-jeromq: Fix tests.
Date: Tue, 6 Mar 2018 23:17:11 +0100 [thread overview]
Message-ID: <CAE4v=phkGHfZR7Nu4RtpRmi3hfVrT16pQ_2TnqFpzR+MgYuxig@mail.gmail.com> (raw)
In-Reply-To: <876068naqg.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
2018-03-06 22:40 GMT+01:00 Ricardo Wurmus <rekado@elephly.net>:
>
> Hi Gábor,
>
> > * gnu/packages/patches/java-jeromq-fix-tests.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Add it.
> > * gnu/packages/java.scm (java-jeromq)[source](patches): Add it.
> > [arguments](#test-exclude): Disable more failing tests.
> > ---
>
> Thank you for this.
>
> > diff --git a/gnu/packages/patches/java-jeromq-fix-tests.patch
> b/gnu/packages/patches/java-jeromq-fix-tests.patch
> > new file mode 100644
> > index 000000000..40fa64801
> > --- /dev/null
> > +++ b/gnu/packages/patches/java-jeromq-fix-tests.patch
> > @@ -0,0 +1,247 @@
>
> It would be good to add some information about the status of this
> patch. Is it part of the next release or will we have to carry this
> patch for a longer time?
>
>
Ok, i will send an updated patch. This is actually in a pull request,
awaiting merge. I think it will make to the next release.
> The patch is also pretty big. Do we need all of it to make jeromq build
> reliably?
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> https://elephly.net
>
>
>
[-- Attachment #2: Type: text/html, Size: 1898 bytes --]
next prev parent reply other threads:[~2018-03-06 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 14:16 bug#30524: java-jeromq: non-deterministic test failures Ricardo Wurmus
2018-03-03 12:58 ` bug#30524: [PATCH] gnu: java-jeromq: Fix tests Gábor Boskovits
2018-03-06 21:40 ` Ricardo Wurmus
2018-03-06 22:17 ` Gábor Boskovits [this message]
2018-03-08 21:06 ` Gábor Boskovits
2018-03-09 20:26 ` Gábor Boskovits
2018-03-10 10:45 ` Gábor Boskovits
2018-03-11 19:13 ` Ricardo Wurmus
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='CAE4v=phkGHfZR7Nu4RtpRmi3hfVrT16pQ_2TnqFpzR+MgYuxig@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=30524@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).