all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: help-guix@gnu.org
Subject: Re: Guix Cuirass - Continuous Integration - Crash Error
Date: Wed, 12 Jun 2019 08:51:48 +0200	[thread overview]
Message-ID: <87ftof9tyz.fsf@elephly.net> (raw)
In-Reply-To: <cd7d03b1-1c64-43ca-8996-3eba54f26e22@www.fastmail.com>


Hi Reza,

> Hi Ludo,
>
> If you had time, could you please have a look at this issue? maybe you
> have an idea about this that.

there is no need to ping the maintainers specifically, especially when
you have already received replies to your request for help.  It’s fine
to ping the list, of course.

>> 2019-06-03T18:50:59 fatal: uncaught exception 'git-error' in 'build'
>> fiber!
>> 2019-06-03T18:50:59 exception arguments: (#<<git-error> code: -14
>> message: "the index is locked; this might be due to a concurrent or
>> crashed process" class: 10>)

Have you checked if this error message reflects the truth about the git
repository in question?  It says that the index is locked.  Have you
looked at the git repository that Cuirass is working on?  Is the index
of that repository locked?  Is another git process accessing the
repository?

--
Ricardo

  reply	other threads:[~2019-06-12  7:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 14:52 Guix Cuirass - Continuous Integration - Crash Error Reza Alizadeh Majd
2019-06-05  9:59 ` Ricardo Wurmus
2019-06-08  5:12   ` Reza Alizadeh Majd
2019-06-08  6:58     ` Ricardo Wurmus
2019-06-09  5:29       ` Reza Alizadeh Majd
2019-06-12  6:09 ` Reza Alizadeh Majd
2019-06-12  6:51   ` Ricardo Wurmus [this message]
2019-06-12 14:50     ` Reza Alizadeh Majd
2019-06-16 14:13       ` Reza Alizadeh Majd

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=87ftof9tyz.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=r.majd@pantherx.org \
    /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.