Mathieu Lirzin <m...@gnu.org> writes: > Hi, > > Mathieu Lirzin <m...@gnu.org> writes: > >> Carlo Zancanaro <ca...@zancanaro.id.au> writes: >> >>> On Thu, Dec 01 2016, ng0 wrote >>>> I tried that before (though I did just think it was wrong) and now I >>>> get the same message as yesterday: >>>> >>>> ... >>>> >>>> In gnu/services/cuirass.scm: 81: 1 [cuirass-shepherd-service #] In >>>> unknown file: ?: 0 [string=? "" ((# # # # ...))] >>>> >>>> ERROR: In procedure string=?: ERROR: In procedure string=: Wrong >>>> type argument in position 2 (expecting string): (((#:name . "guix") >>>> (#:url . "git://git.savannah.gnu.org/guix.git") (#:load-path . ".") >>>> (#:file . "/.../cuirass/tests/gnu-system.scm") (#:proc . hydra-jobs) >>>> (#:arguments (subset . "hello")) (#:branch . "master"))) >>> >>> It looks like cuirass is expecting the specifications to be a string, >>> not a list. I don't know anything about cuirass, so I can't help you >>> to configure the cuirass-service. >>> >>> Looking at the source, specifications has a comment ";string >>> (file-name)". It looks like the "specifications" field of the >>> configuration is just equivalent to the --specifications argument to the >>> cuirass command, if that helps at all. >> >> Indeed, this is a mistake on my side. Here are 2 patches that should >> fix this issue. > > I went ahead and pushed them in commits: > > - 44ccd9622eb4a0083d4f833a61172973390ca62b > - 57aa94bd7e7d530e52356723c8f1dbf727144b25 > > Thanks, > > -- > Mathieu Lirzin >
Thanks, I wasn't able to test them before and provide you with feedback, I was just busy and the CI is kind of low priority for gnunet. But we'd like to get a CI running on our own infrastructure on systems like GuixSD as far as I understood conversations so far. But I am aware that a general CI might still take some time with cuirass. -- ♥Ⓐ ng0 | ng0.chaosnet.org
