From: Felix Lechner via Guix-patches via <guix-patches@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 61989@debbugs.gnu.org
Subject: [bug#61989] [PATCH 00/11] Adding Gocryptfs (feature branch)
Date: Sat, 11 Mar 2023 21:27:19 -0800 [thread overview]
Message-ID: <CAFHYt56LSu61Tu8KwMXrEyoMSSYe4r4crS0PNkHOjHeCAw-HTw@mail.gmail.com> (raw)
In-Reply-To: <ZAypsC9xozBJvIMv@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
Hi Leo,
On Sat, Mar 11, 2023 at 8:17 AM Leo Famulari <leo@famulari.name> wrote:
>
> I rebased the branch and pushed again. Maybe the
> building of all these non-Go packages was spurious (this can happen with
> Cuirass), and we'll see a more clear result this time.
Thanks for doing that! The results look much better, but I believe
some of the failures are still unrelated to our feature branch.
I cloned the wip-go-updates branch and successfully built pigx-rnaseq
on my own equipment even though Cuirass showed failing tests. [1] A
partial log is attached.
Kind regards
Felix Lechner
[1] https://ci.guix.gnu.org/build/533474/details
[-- Attachment #2: pigx-rnaseq.log.xz --]
[-- Type: application/octet-stream, Size: 29572 bytes --]
next prev parent reply other threads:[~2023-03-12 5:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 20:52 [bug#61989] [PATCH 00/11] Adding Gocryptfs (feature branch) Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 01/11] gnu: go-golang-org-x-sys: Update to 0.4.0 Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 02/11] gnu: go-golang-org-x-net: Update to 0.5.0 Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 03/11] gnu: Add go-github-com-hanwen-go-fuse-v2 Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 04/11] gnu: Add go-github-com-aperturerobotics-jacobsa-crypto Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 05/11] gnu: Add go-github-com-jacobsa-oglematchers Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 06/11] gnu: Add go-github-com-jacobsa-oglemock Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 07/11] gnu: Add go-github-com-jacobsa-ogletest Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 08/11] gnu: Add go-github-com-jacobsa-reqtrace Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 09/11] gnu: Add go-github-com-pkg-xattr Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 10/11] gnu: Add go-github-com-rfjakob-eme Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 11/11] gnu: Add gocryptfs Felix Lechner via Guix-patches via
2023-03-06 16:42 ` [bug#61989] [PATCH 00/11] Adding Gocryptfs (feature branch) Leo Famulari
2023-03-07 23:06 ` Leo Famulari
2023-03-08 0:02 ` Felix Lechner via Guix-patches via
2023-03-08 15:10 ` Leo Famulari
2023-03-10 0:21 ` Felix Lechner via Guix-patches via
2023-03-10 1:54 ` Leo Famulari
2023-03-11 16:17 ` Leo Famulari
2023-03-12 5:27 ` Felix Lechner via Guix-patches via [this message]
2023-03-14 2:05 ` Felix Lechner via Guix-patches via
2023-03-16 1:21 ` Leo Famulari
2023-03-16 19:44 ` Felix Lechner via Guix-patches via
2023-03-16 23:59 ` Leo Famulari
2023-03-17 19:02 ` Felix Lechner via Guix-patches via
2023-03-19 8:51 ` Efraim Flashner
2023-03-19 17:17 ` Leo Famulari
2023-03-19 17:22 ` Leo Famulari
2023-03-19 17:25 ` Felix Lechner via Guix-patches via
2023-03-19 20:38 ` Leo Famulari
2023-03-19 20:46 ` Leo Famulari
2023-03-19 20:48 ` Felix Lechner via Guix-patches via
2023-03-19 20:51 ` Leo Famulari
2023-03-19 20:54 ` Felix Lechner via Guix-patches via
2023-03-19 21:04 ` Leo Famulari
2023-03-19 21:31 ` Felix Lechner via Guix-patches via
2023-03-28 20:37 ` bug#61989: " Leo Famulari
2023-03-28 20:54 ` [bug#61989] " Felix Lechner via Guix-patches via
2023-03-13 17:53 ` Leo Famulari
2023-03-13 20:37 ` Felix Lechner via Guix-patches via
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=CAFHYt56LSu61Tu8KwMXrEyoMSSYe4r4crS0PNkHOjHeCAw-HTw@mail.gmail.com \
--to=guix-patches@gnu.org \
--cc=61989@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=leo@famulari.name \
/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).