[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Progress on 'guix deploy'
From: |
Jakob L. Kreuze |
Subject: |
Re: Progress on 'guix deploy' |
Date: |
Tue, 11 Jun 2019 16:54:36 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) |
Ludovic Courtès <address@hidden> writes:
> Could it be that the VM died in the middle of the SSH session? Where
> does SIGTERM (15) come from?
The SIGTERM comes from my less-than-ideal way of spinning up marionettes
outside of the derivation that carries out the srfi-64 tests,
'call-with-marionette'. I have a line with '(kill pid SIGTERM)' as the
QEMU guest will otherwise continue to run after the test suite exits. I
commented out the line and verified that after the error occurs, the
guest is still running (and accessible via SSH).
What's interesting is, if I leave the guest running, SSH in, set up
public key auth and run 'guix deploy' from my shell, I don't get the
socket error.
#+BEGIN_SRC
jakob@Epsilon ~/Code/guix [env] $ ./pre-inst-env guix deploy
~/Notes/Software/Guix/deployment.scm
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
@ build-started /gnu/store/4cl8yydsdnz9rwsswrgr788l7p2q2xqy-etc.drv -
x86_64-linux /var/log/guix/drvs/4c//l8yydsdnz9rwsswrgr788l7p2q2xqy-etc.drv.bz2
23724
@ build-succeeded /gnu/store/4cl8yydsdnz9rwsswrgr788l7p2q2xqy-etc.drv -
@ build-started
/gnu/store/ban0c1b97gfzy5siqwzd30j3m31slxfq-activate-service.drv - x86_64-linux
/var/log/guix/drvs/ba//n0c1b97gfzy5siqwzd30j3m31slxfq-activate-service.drv.bz2
23732
@ build-succeeded
/gnu/store/ban0c1b97gfzy5siqwzd30j3m31slxfq-activate-service.drv -
@ build-started /gnu/store/8wadw74kz2nwx6n7gmilkjn4qig3isrn-activate.drv -
x86_64-linux
/var/log/guix/drvs/8w//adw74kz2nwx6n7gmilkjn4qig3isrn-activate.drv.bz2 23739
@ build-succeeded /gnu/store/8wadw74kz2nwx6n7gmilkjn4qig3isrn-activate.drv -
@ build-started /gnu/store/yz4brqis8jfs08wjhyk1bbdcz6vdx2ld-boot.drv -
x86_64-linux /var/log/guix/drvs/yz//4brqis8jfs08wjhyk1bbdcz6vdx2ld-boot.drv.bz2
23745
@ build-succeeded /gnu/store/yz4brqis8jfs08wjhyk1bbdcz6vdx2ld-boot.drv -
@ build-started /gnu/store/dqxm5lw45408f64lqm5k2ylyx7vvqpyw-system.drv -
x86_64-linux
/var/log/guix/drvs/dq//xm5lw45408f64lqm5k2ylyx7vvqpyw-system.drv.bz2 23751
@ build-succeeded /gnu/store/dqxm5lw45408f64lqm5k2ylyx7vvqpyw-system.drv -
building gnu-deployed... done
sending 4790 store items (1,905 MiB) to 'localhost'...
Backtrace:
10 (primitive-load "/home/jakob/.config/guix/current/bin/g…")
In guix/ui.scm:
1747:12 9 (run-guix-command _ . _)
In guix/store.scm:
623:10 8 (call-with-store _)
In srfi/srfi-1.scm:
640:9 7 (for-each #<procedure 5088840 at guix/scripts/deploy.s…> …)
In guix/scripts/deploy.scm:
84:20 6 (_ _)
In guix/store.scm:
1794:24 5 (run-with-store _ _ #:guile-for-build _ #:system _ # _)
In gnu/machine.scm:
119:2 4 (_ _)
In guix/store.scm:
1690:38 3 (_ #<store-connection 256.99 3187000>)
In guix/ssh.scm:
313:4 2 (send-files _ _ _ #:recursive? _ #:log-port _)
In guix/store.scm:
1562:12 1 (export-paths #<store-connection 256.99 3187000> _ #<i…> …)
1542:22 0 (export-path #<store-connection 256.99 3187000> _ #<in…> …)
guix/store.scm:1542:22: In procedure export-path:
Throw to key `srfi-34' with args `(#<condition &store-protocol-error [message:
"hash of path `/gnu/store/ag8ilfwcnxn0xnw8bar9ia73h3hg3rra-gs-fonts-8.11' has
changed from `67ae533629b1f24d9736c6daf5f6439e5cfce18c7fa2f1c6d45e65bbf0c471b8'
to `dd9339c8d709b867f3ff056b2f2e1aa368cfa2312302fc30392d820c2f3ef9ab'!" status:
1] 8093d20>)'.
#+END_SRC
Very unusal. I'm wondering if it's caused by my use of
'call-with-connected-session/auth' from (gnu tests ssh) rather than
'open-ssh-session' in (guix ssh). That's the main difference between the
test suite and 'guix deploy' in terms of how they communicate with the
guest.
Regards,
Jakob
signature.asc
Description: PGP signature