Danny, 2018-01-01 0:39 GMT+01:00 Danny Milosavljevic : > Try this: > > diff --git a/gnu/build/linux-boot.scm b/gnu/build/linux-boot.scm > index 4dd740174..810a0d63f 100644 > --- a/gnu/build/linux-boot.scm > +++ b/gnu/build/linux-boot.scm > @@ -507,7 +507,14 @@ to it are lost." > (switch-root "/root") > (format #t "loading '~a'...\n" to-load) > > - (primitive-load to-load) > + (catch #t > + (lambda () > + (primitive-load to-load)) > + (lambda (key . args) > + (format (current-error-port) "Error: ~a: ~a\n" key args) > + (reboot)) > + (lambda (key . args) > + (display-backtrace (make-stack #t) > (current-error-port)))) > > (format (current-error-port) > "boot program '~a' terminated, rebooting~%" > thank you so much for this ! I don't know if it' s current anymore, though In fact, I have discovered some errors I made in the code Now the trytond test succeeds (yay !) and I don't get ushered in a REPL anymore There wee seveal problems First, I hadn't pdated gnulocal.mk with my new files gnu/services/trytond.scm gnu/tests/trytond.scm Also the Gexpression used in my trytond activation was garbled, so the shepherd serrvice coldn't run As a consequence, in the test definition this piece of code (marionette-eval '(begin (use-modules (gnu services herd)) (match (start-service 'trytond) (#f #f) (('service response-parts ...) (match (assq-ref response-parts 'running) ((pid) (number? pid)))))) marionette)) didn't succeed. In the match clause, the (#f #f) case ensued (I suppose) I discovered all this by creating a virtual machine based on my trytond branch and running it manually After I fixed all these glitches, the system test run as a charm So now I'm a bit overwhelmed and I don't know if your suggestion is still currrent I can tell you, though, that I feel very reassured by the fact that someone tried to help me out ! I'll keep your suggestion in mind, should I have any further problems with the marionette service Happy New Year ! Ciao Cato