Guix Cuirass - Continuous Integration - Crash Error

Guix Cuirass - Continuous Integration - Crash Error

[Reza Alizadeh Majd]

Hi Guix, 

I want to setup a CI build server using _Cuirass_ to build a series of custom 
packages for Guix. but I receive following error and cuirass-service crashes, 
could anyone help me on this? 

```
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>)
In ice-9/boot-9.scm:
    829:9  9 (catch _ _ #<procedure 2da2560 at cuirass/utils.scm:17?> ?)
    705:2  8 (call-with-prompt _ _ #<procedure 2da2240 at ice-9/eval?>)
    705:2  7 (call-with-prompt _ _ #<procedure 2dab940 at ice-9/eval?>)
In ice-9/eval.scm:
    619:8  6 (_ #(#(#<directory (guile-user) 236e140> #<variable?> ?)))
In srfi/srfi-1.scm:
    640:9  5 (for-each #<procedure process (spec)> (((#:name . #) ?)))
In ice-9/boot-9.scm:
   751:25  4 (dispatch-exception 0 git-error (#<<git-error> code: -?>))
In cuirass/utils.scm:
    181:8  3 (_ _ #<<git-error> code: -14 message: "the index is loc?>)
In ice-9/boot-9.scm:
    829:9  2 (catch #t #<procedure 2dd44e0 at cuirass/utils.scm:181?> ?)
In cuirass/utils.scm:
   182:22  1 (_)
In unknown file:
           0 (make-stack #t)
ERROR: In procedure make-stack:
Git error: the index is locked; this might be due to a concurrent or crashed process
```


In case that it might be helpful, here is my `%cuirass-specs` definition: 
```
(define %cuirass-specs
   #~(list '((#:name . "my-manifest")
             (#:load-path-inputs . ("guix"))
             (#:package-path-inputs . ("custom-packages"))
             (#: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 . "pantherx")
                           (#:url . "https://user:pass@git.pantherx.org/development/guix-pantherx.git")
                           (#:load-path . ".")
                           (#:branch . "master")
                           (#:no-compile? #t)))))))
. . .

(service cuirass-service-type
			    (cuirass-configuration
			      (interval 10)
			      (use-substitutes? #t)
			      (port 8082)
			      (host "0.0.0.0")
			      (specifications %cuirass-specs)))
```


I also added `manifest.scm` file beside my system configuration file with following
content:
```
(use-modules (px packages accounts))
(packages->manifest
   (list px-accounts))
```


---
Best, 
Reza

Re: Guix Cuirass - Continuous Integration - Crash Error

[Ricardo Wurmus]

Hi Reza,

> I want to setup a CI build server using _Cuirass_ to build a series of custom 
> packages for Guix. but I receive following error and cuirass-service crashes, 
> could anyone help me on this? 
>
> ```
> 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>)

Try erasing the cache directories containing the git repositories.

-- 
Ricardo

Re: Guix Cuirass - Continuous Integration - Crash Error

[Reza Alizadeh Majd]

Hi Ricardo, 

Thanks for your response. 
 
> Try erasing the cache directories containing the git repositories.

unfortunately using `guix gc -C` wouldn't  be helpful, and cuirass service still 
fails with same error. 

Best, 
Reza

Re: Guix Cuirass - Continuous Integration - Crash Error

[Ricardo Wurmus]

Hi Reza,

>> Try erasing the cache directories containing the git repositories.
>
> unfortunately using `guix gc -C` wouldn't  be helpful, and cuirass service still
> fails with same error.

The cache directories are not affected by “guix gc”.  The default cache
directory when using the cuirass service on Guix System is
’/var/cache/cuirass’.

--
Ricardo

Re: Guix Cuirass - Continuous Integration - Crash Error

[Reza Alizadeh Majd]

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

Re: Guix Cuirass - Continuous Integration - Crash Error

[Reza Alizadeh Majd]

Hi Ludo, 

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

I really need to setup a custom build server for Guix, since our custom package definitions are increasing, and it's not efficient to build every package from source for each user. 

Thanks, 
Reza



On Mon, Jun 3, 2019, at 7:23 PM, Reza Alizadeh Majd wrote:
> Hi Guix, 
> 
> I want to setup a CI build server using _Cuirass_ to build a series of custom 
> packages for Guix. but I receive following error and cuirass-service crashes, 
> could anyone help me on this? 
> 
> ```
> 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>)
> In ice-9/boot-9.scm:
>     829:9  9 (catch _ _ #<procedure 2da2560 at cuirass/utils.scm:17?> ?)
>     705:2  8 (call-with-prompt _ _ #<procedure 2da2240 at ice-9/eval?>)
>     705:2  7 (call-with-prompt _ _ #<procedure 2dab940 at ice-9/eval?>)
> In ice-9/eval.scm:
>     619:8  6 (_ #(#(#<directory (guile-user) 236e140> #<variable?> ?)))
> In srfi/srfi-1.scm:
>     640:9  5 (for-each #<procedure process (spec)> (((#:name . #) ?)))
> In ice-9/boot-9.scm:
>    751:25  4 (dispatch-exception 0 git-error (#<<git-error> code: -?>))
> In cuirass/utils.scm:
>     181:8  3 (_ _ #<<git-error> code: -14 message: "the index is loc?>)
> In ice-9/boot-9.scm:
>     829:9  2 (catch #t #<procedure 2dd44e0 at cuirass/utils.scm:181?> ?)
> In cuirass/utils.scm:
>    182:22  1 (_)
> In unknown file:
>            0 (make-stack #t)
> ERROR: In procedure make-stack:
> Git error: the index is locked; this might be due to a concurrent or 
> crashed process
> ```
> 
> 
> In case that it might be helpful, here is my `%cuirass-specs` 
> definition: 
> ```
> (define %cuirass-specs
>    #~(list '((#:name . "my-manifest")
>              (#:load-path-inputs . ("guix"))
>              (#:package-path-inputs . ("custom-packages"))
>              (#: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 . "pantherx")
>                            (#:url . 
> "https://user:pass@git.pantherx.org/development/guix-pantherx.git")
>                            (#:load-path . ".")
>                            (#:branch . "master")
>                            (#:no-compile? #t)))))))
> . . .
> 
> (service cuirass-service-type
> 			    (cuirass-configuration
> 			      (interval 10)
> 			      (use-substitutes? #t)
> 			      (port 8082)
> 			      (host "0.0.0.0")
> 			      (specifications %cuirass-specs)))
> ```
> 
> 
> I also added `manifest.scm` file beside my system configuration file 
> with following
> content:
> ```
> (use-modules (px packages accounts))
> (packages->manifest
>    (list px-accounts))
> ```
> 
> 
> ---
> Best, 
> Reza
> 
> 
>

Re: Guix Cuirass - Continuous Integration - Crash Error

[Ricardo Wurmus]

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

Re: Guix Cuirass - Continuous Integration - Crash Error

[Reza Alizadeh Majd]

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

Re: Guix Cuirass - Continuous Integration - Crash Error

[Reza Alizadeh Majd]

Do I need to post a new email for this later problem? 

maybe it receives a better feedback, plus a better reference for others in the future with same issue? 

Best, 
Reza


On Wed, Jun 12, 2019, at 7:25 PM, Reza Alizadeh Majd wrote:
> 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
> 
> 
>