unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 30107@debbugs.gnu.org
Subject: bug#30107: ant-bootstrap@1.7.1 sometimes fails to build on core-updates
Date: Sun, 14 Jan 2018 10:32:03 +0100	[thread overview]
Message-ID: <CAE4v=pg9Jk+xTj74zW1v1egzK_=w-JNkyXQoWyDXAdXB90No4w@mail.gmail.com> (raw)
In-Reply-To: <87o9lxapul.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

I've also seen this once. No idea so far.
I've tried to look around, but found no other mention of this issue.

2018-01-14 7:58 GMT+01:00 Chris Marusich <cmmarusich@gmail.com>:

> Hi,
>
> At commit 1b321229f4653c5daa873813e24910789c0b2918 (i.e., the current
> tip of the core-updates branch), ant-bootstrap@1.7.1 sometimes fails to
> build.  This package is defined in gnu/packages/java.scm, but it is not
> exported (i.e., it is used privately within the module).  Note that
> according to 'guix refresh', currently 215 packages depend on this
> package.
>
> I tried to build this package 147 times.  It failed 5 times, and it
> succeeded 142 times.  That's about a 3% failure rate.  All 5 failures
> produced the same log output, which I've attached.  My machine is an
> x86-64 machine.
>
> --
> Chris
>

[-- Attachment #2: Type: text/html, Size: 1252 bytes --]

  reply	other threads:[~2018-01-14  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-14  6:58 bug#30107: ant-bootstrap@1.7.1 sometimes fails to build on core-updates Chris Marusich
2018-01-14  9:32 ` Gábor Boskovits [this message]
2018-01-18  9:02 ` bug#30107: Another kind of failure Gábor Boskovits
2018-01-26 10:30 ` bug#30107: Backtrace Björn Höfling
2018-02-03  8:36 ` bug#30107: How I got the core dump Björn Höfling

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=pg9Jk+xTj74zW1v1egzK_=w-JNkyXQoWyDXAdXB90No4w@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=30107@debbugs.gnu.org \
    --cc=cmmarusich@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 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).