From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Reza Alizadeh Majd" Subject: Re: Guix Cuirass - Continuous Integration - Crash Error Date: Wed, 12 Jun 2019 19:20:35 +0430 Message-ID: <93b699ac-28fe-4b58-8fda-453af99b772f@www.fastmail.com> References: <9911e842-987e-48c4-8df0-8f1a6aa9086a@www.fastmail.com> <87ftof9tyz.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:55250) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hb4aL-0000Wq-17 for help-guix@gnu.org; Wed, 12 Jun 2019 10:50:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hb4aF-0001NT-GK for help-guix@gnu.org; Wed, 12 Jun 2019 10:50:41 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:43757) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hb4aF-0001J4-3E for help-guix@gnu.org; Wed, 12 Jun 2019 10:50:39 -0400 In-Reply-To: <87ftof9tyz.fsf@elephly.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ricardo Wurmus Cc: help-guix@gnu.org Hi Ricardo, Sorry I thought it might be helpful. lastly I think I find this issue's source, it seems that there was an issue about definition and usage of inputs. I tried to define spec from scratch and run cuirass manually. here is my new sample spec definition: ``` (define my-spec '((#:name . "my-manifest") (#:load-path-inputs . ("guix")) (#:package-path-inputs . ("guix")) (#:proc-input . "guix") (#:proc-file . "build-aux/cuirass/gnu-system.scm") (#:proc . cuirass-jobs) (#:proc-args . ((subset . "hello") (systems . ("x86_64-linux")))) (#:inputs . (((#:name . "guix") (#:url . "git://git.savannah.gnu.org/guix.git") (#:load-path . ".") (#:branch . "master") (#:no-compile? . #t)))))) (list my-spec) ``` and I run cuirass manually using following command: ``` $ cuirass --databas=mytest.db --specifications=my-spec.scm ``` now I receive following warnings when running above command: ``` 2019-06-12T19:06:03 running Fibers on 4 kernel threads 2019-06-12T19:06:03 marking stale builds as "scheduled"... 2019-06-12T19:06:03 listening on 0.0.0.0:8082 2019-06-12T19:06:03 retrieving list of pending builds... 2019-06-12T19:06:03 heap: 11.00 MiB; threads: 10; file descriptors: 49 2019-06-12T19:06:03 canceling 0 stale builds 2019-06-12T19:06:03 restarting 0 pending builds 2019-06-12T19:06:03 building 0 derivations in batches of 200 2019-06-12T19:06:03 done with 0 derivations 2019-06-12T19:06:03 done with restarted builds 2019-06-12T19:06:03 fetching input 'guix' of spec 'my-manifest' 2019-06-12T19:06:04 fetched input 'guix' of spec 'my-manifest' (commit "798b80cea2ebf4a2303cef94468803cd50a51f7d") 2019-06-12T19:06:04 next evaluation in 30 seconds 2019-06-12T19:06:04 evaluating spec 'my-manifest' `_IOLBF' is deprecated. Use the symbol 'line instead. warning: failed to load '(build-aux build-self)': no code for module (build-aux build-self) warning: failed to load '(build-aux build-self)': no code for module (build-aux build-self) warning: failed to load '(build-aux check-available-binaries)': no code for module (build-aux check-available-binaries) checking final inputs for 'x86_64-linux'... checking final inputs for 'i686-linux'... checking final inputs for 'armhf-linux'... warning: failed to load '(build-aux check-final-inputs-self-contained)': no code for module (build-aux check-final-inputs-self-contained) ``` is it possible that I missed something? Thanks, Reza