From: Leo Famulari <leo@famulari.name>
To: 45559@debbugs.gnu.org
Subject: bug#45559: Cuirass has not successfully evaluated the stagig branch in 3 weeks
Date: Sun, 3 Jan 2021 17:14:18 -0500 [thread overview]
Message-ID: <X/JBusRAB8+qtvDf@jasmine.lan> (raw)
In-Reply-To: <X+zkQsNMWTiLX4IF@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]
I was granted shell access to the Berlin server.
I have been building substitutes for the staging branch from the Git
tree at /home/lfam/staging
I noticed that Cuirass is doing *something* with the staging branch, but
it doesn't seem to have any result that I can observe from the interface
at ci.guix.gnu.org, and package substitutes do not appear.
------
$ ps aux | grep staging
[...]
cuirass 54325 0.0 0.1 509928 223724 ? Sl 2020 0:21 /gnu/store/0w76khfspfy8qmcpjya41chj3bgfcy0k-guile-3.0.4/bin/guile --no-auto-compile -e main -s /gnu/store/q2qkcwd82p52x8kdar5kmmhrx464p0vk-cuirass-dev-0.0.1-57.697fa14/bin/evaluate ((#:name . "staging-staging") (#:load-path-inputs) (#:package-path-inputs) (#:proc-input . "staging") (#:proc-file . "build-aux/cuirass/gnu-system.scm") (#:proc . cuirass-jobs) (#:proc-args (systems "x86_64-linux" "i686-linux" "aarch64-linux" "armhf-linux")) (#:inputs ((#:name . "staging") (#:url . "https://git.savannah.gnu.org/git/guix.git") (#:load-path . ".") (#:branch . "staging") (#:tag . #f) (#:commit . #f) (#:no-compile? . #t))) (#:build-outputs)) (((#:input . "staging") (#:directory . "/gnu/store/13961d848pgzrbqw4bs4kniv4i4cch9z-guix-64e995b") (#:commit . "64e995b4cf473c7f52bad0dea8c27eea6eee662c") (#:timestamp . 1609327975) (#:load-path . ".") (#:no-compile? . #t)))
cuirass 62079 0.0 0.1 507644 233260 pts/8 Sl Jan02 0:17 /gnu/store/5iisqr9wn9bgg9h52fw86why1xih1gvi-profile/bin/guile --no-auto-compile -e main -s /home/mathieu/cuirass/bin/evaluate ((#:name . "staging-staging") (#:load-path-inputs) (#:package-path-inputs) (#:proc-input . "staging") (#:proc-file . "build-aux/cuirass/gnu-system.scm") (#:proc . cuirass-jobs) (#:proc-args (systems "x86_64-linux" "i686-linux" "aarch64-linux")) (#:inputs ((#:name . "staging") (#:url . "https://git.savannah.gnu.org/git/guix.git") (#:load-path . ".") (#:branch . "staging") (#:tag . #f) (#:commit . #f) (#:no-compile? . #t))) (#:build-outputs) (#:priority . 3)) (((#:input . "staging") (#:directory . "/gnu/store/13961d848pgzrbqw4bs4kniv4i4cch9z-guix-64e995b") (#:commit . "64e995b4cf473c7f52bad0dea8c27eea6eee662c") (#:timestamp . 1609610295) (#:load-path . ".") (#:no-compile? . #t)))
------
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-03 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 20:34 bug#45559: Cuirass has not successfully evaluated the stagig branch in 3 weeks Leo Famulari
2021-01-03 22:14 ` Leo Famulari [this message]
2021-01-04 9:19 ` Mathieu Othacehe
2021-01-04 14:08 ` Leo Famulari
2021-01-04 14:35 ` Mathieu Othacehe
2021-01-05 3:59 ` Leo Famulari
2021-01-05 6:39 ` Mathieu Othacehe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X/JBusRAB8+qtvDf@jasmine.lan \
--to=leo@famulari.name \
--cc=45559@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).