unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: 61989@debbugs.gnu.org
Subject: [bug#61989] [PATCH 00/11] Adding Gocryptfs (feature branch)
Date: Thu, 9 Mar 2023 20:54:28 -0500	[thread overview]
Message-ID: <ZAqN1LBQfnROP5g+@jasmine.lan> (raw)
In-Reply-To: <CAFHYt54B11OZy6rsAfQ8xGAihgaKoFthzj4Op129jzPBQoNowg@mail.gmail.com>

On Thu, Mar 09, 2023 at 04:21:20PM -0800, Felix Lechner wrote:
> I did mention the Cuirass question on IRC as you had asked, but no one
> seemed to remember. Then I addressed the Haskell failure by responding
> to a recent thread about that upload. [2] By your reply, I know that
> you saw my message.

Thanks for working on those leads!

In my reply to your message regarding Haskell, I CC-ed Mathieu Othacehe,
who is relatively active developing Cuirass and assists with operations
on ci.guix.gnu.org.  Let's see if he replies.

I do see that on ci.guix.gnu.org, we are running Cuirass
1.1.0-13.1341725, which should respect the max-silent-time property.
According to NEWS, this was added in Cuirass 1.0.0.

One might consider trying to debug a local installation of Cuirass, to
see if it actually respects this property. Imagine a test package that
sleeps for 10 seconds in a build phase but has a max-silent-time of 5.

In the meantime, I would check that gocryptfs is working satisfactorily
based on the branch.

I was surprised that Cuirass tried to build GHC and all these R packages
as a result of these patches. Do you know if these packages (e.g. GHC)
depend on Go somehow?




  reply	other threads:[~2023-03-10  1:55 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 [this message]
2023-03-11 16:17             ` Leo Famulari
2023-03-12  5:27               ` Felix Lechner via Guix-patches via
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=ZAqN1LBQfnROP5g+@jasmine.lan \
    --to=leo@famulari.name \
    --cc=61989@debbugs.gnu.org \
    --cc=felix.lechner@lease-up.com \
    /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).