From: Chris Marusich <cmmarusich@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 30030@debbugs.gnu.org
Subject: [bug#30030] [PATCH core-updates] gnu: java-jeromq: Update to 0.4.3.
Date: Tue, 23 Jan 2018 00:06:04 -0800 [thread overview]
Message-ID: <87lggp579v.fsf@garuda.local.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20180108201529.11328-1-boskovits@gmail.com> ("Gábor Boskovits"'s message of "Mon, 8 Jan 2018 21:15:29 +0100")
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Gábor Boskovits <boskovits@gmail.com> writes:
> * gnu/packages/java.scm (java-jeromq): Update to 0.4.3.
Unfortunately, when this patch is applied to commit
f3cd6633ce7348fb92735d6cd708bdc8b3b063ee (the current tip of
core-updates), the "check" phase of the build fails. Actually, it fails
even before the patch, so you this change doesn't break it.
The failures are not deterministic. Various classes fail, and it's not
always the same one every time. I briefly looked at the failures, and I
couldn't make much sense of it. I think there are two avenues of
investigation:
1) Git bisect to find out which commit introduced the break.
2) Report the failure(s) upstream.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-01-23 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 20:15 [bug#30030] [PATCH core-updates] gnu: java-jeromq: Update to 0.4.3 Gábor Boskovits
2018-01-23 8:06 ` Chris Marusich [this message]
2018-01-23 8:26 ` Gábor Boskovits
2018-03-03 17:52 ` bug#30030: Closing, already upstream Gábor Boskovits
2018-03-08 11:38 ` [bug#30030] [PATCH] gnu: java-jeromq: Fix tests Gábor Boskovits
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=87lggp579v.fsf@garuda.local.i-did-not-set--mail-host-address--so-tickle-me \
--to=cmmarusich@gmail.com \
--cc=30030@debbugs.gnu.org \
--cc=boskovits@gmail.com \
/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.