unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Reza Alizadeh Majd <r.majd@pantherx.org>
To: help-guix mailing list <help-guix@gnu.org>
Subject: Re: Problem on setting up the Cuirass as substitute server
Date: Fri, 27 Nov 2020 15:27:02 +0330	[thread overview]
Message-ID: <20201127152702.260d1c3d@panther-arch.localdomain> (raw)
In-Reply-To: <20201126185650.2a80b05a@panther-arch.localdomain>

On Thu, 26 Nov 2020 18:56:50 +0330
Reza Alizadeh Majd <r.majd@pantherx.org> wrote:

> --8<---------------cut here---------------start------------->8---
> (define %cuirass-specs
>   #~(list
>      '((#:name . "my-manifest")
>        (#:load-path-inputs . ("guix"))
>        (#:package-path-inputs . ())
>        (#:proc-input . "guix")
>        (#:proc-file . "build-aux/cuirass/gnu-system.scm")
>        (#:proc . cuirass-jobs)
>        (#:proc-args . ((subset . "manifests")
>                        (systems . ("x86_64-linux"))
>                        (manifests . (("config" . "manifest.scm")))))
>        (#:inputs . (((#:name . "guix")
>                      (#:url . "git://git.savannah.gnu.org/guix.git")
>                      (#:load-path . ".")
>                      (#:branch . "master")
>                      (#:no-compile? . #t))
>                     ((#:name . "config")
>                      (#:url .
> "https://github.com/ramajd/guix-manifest.git") (#:load-path . ".")
>                      (#:branch . "master")
>                      (#:no-compile? . #t)))))))
> --8<---------------cut here---------------end--------------->8---

add the `(#:build-outputs . ())` to my specification definition, cuirass
added my specification to the list of it's build specs. 

my current problem is that status of added jobs are `scheduled` and I
receive following message on cuirass logs:

--8<---------------cut here---------------start------------->8---
2020-11-27T15:14:19 evaluation 1 for 'my-manifest' completed
2020-11-27T15:14:19 building 2 jobs for 'my-manifest'
2020-11-27T15:14:19 Registering builds for evaluation 1.
2020-11-27T15:14:19 evaluation 1 registration took 0.001742 seconds
2020-11-27T15:14:19 evaluation 1 registered 2 new derivations
2020-11-27T15:14:19 building 2 derivations in batches of 200
2020-11-27T15:14:19 building batch of 200 derivations (0/2)
2020-11-27T15:14:20 done with 2 derivations
2020-11-27T15:14:20 outputs:
/gnu/store/220zbr30p8yj6yg9ndkk7a537x6f4vir-ungoogled-chromium-87.0.4280.66-0.1f7cdef
/gnu/store/a462kby1q51ndvxdv3b6p0rsixxrgx1h-hello-2.10
2020-11-27T15:14:20 success: 0, fail: 2
--8<---------------cut here---------------end--------------->8---

I assume this happened because that my server used available substitutes
from Guix substitute server, instead of building them by itself. is
that right?  

if not, is there any further thing that I need to apply on my spec
definition? 

Regards, 
Reza


-- 
Reza Alizadeh Majd
PantherX Team
https://www.pantherx.org/


  reply	other threads:[~2020-11-27 11:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 15:26 Problem on setting up the Cuirass as substitute server Reza Alizadeh Majd
2020-11-27 11:57 ` Reza Alizadeh Majd [this message]
2020-12-20 21:09   ` Joshua Branson

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=20201127152702.260d1c3d@panther-arch.localdomain \
    --to=r.majd@pantherx.org \
    --cc=help-guix@gnu.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.
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).