From: "Reza Alizadeh Majd" <r.majd@pantherx.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Guix Cuirass - Continuous Integration - Crash Error
Date: Sun, 09 Jun 2019 09:59:44 +0430 [thread overview]
Message-ID: <c5d08cd4-7d0e-4a20-bc37-e7794836a18a@www.fastmail.com> (raw)
In-Reply-To: <87blz88swj.fsf@elephly.net>
Hi,
> The cache directories are not affected by “guix gc”. The default cache
> directory when using the cuirass service on Guix System is
Unfortunately clearing the cache wouldn't help. maybe I had a mistake on
definition of `$cuirass-spec` or manifest file.
Best,
Reza
next prev parent reply other threads:[~2019-06-09 5:29 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 [this message]
2019-06-12 6:09 ` Reza Alizadeh Majd
2019-06-12 6:51 ` Ricardo Wurmus
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
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=c5d08cd4-7d0e-4a20-bc37-e7794836a18a@www.fastmail.com \
--to=r.majd@pantherx.org \
--cc=help-guix@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.
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).