From: Lars-Dominik Braun <lars@6xq.net>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Simon Tournier <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Subject: Re: Merging branch wip-haskell
Date: Wed, 8 Mar 2023 20:31:33 +0100 [thread overview]
Message-ID: <ZAjildvCQiotaBff@noor.fritz.box> (raw)
In-Reply-To: <CAFHYt54Mm4noeXztAF5b-f7zDEp+=0iqqzupqBqOedUrdkTxLg@mail.gmail.com>
Hello Felix,
> I see build failures [1] for Ghc 9.2.5 in the Cuirass job set [2] for
> my own feature branch. [3] They are caused by a one-hour timeout. Did
> you folks figure out how to extend the timeout limit on Cuirass when
> working on your own branch? Thanks!
I don’t see GHC being rebuild in [2] and GHC 9.2 should
have a higher max-silent-time than 1 hour on master since
3bb2078a12d78a13f1e1520fe3705333a74ef6e3 (which is part of your
branch). So I’m slightly confused.
Cheers,
Lars
> [1] https://ci.guix.gnu.org/build/478772/log/raw
> [2] https://ci.guix.gnu.org/eval/262309
> [3] https://git.savannah.gnu.org/cgit/guix.git/log/?h=wip-go-updates
next prev parent reply other threads:[~2023-03-08 19:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 9:01 Merging branch wip-haskell Lars-Dominik Braun
2023-02-15 9:31 ` Andreas Enge
2023-02-15 9:45 ` Lars-Dominik Braun
2023-02-15 9:48 ` Andreas Enge
2023-02-15 10:38 ` zimoun
2023-02-22 9:37 ` Andreas Enge
2023-02-22 10:54 ` Efraim Flashner
2023-03-07 20:24 ` Andreas Enge
2023-02-26 9:47 ` Lars-Dominik Braun
2023-02-27 10:47 ` Simon Tournier
2023-02-27 11:04 ` Lars-Dominik Braun
2023-02-27 11:55 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-08 17:51 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-08 19:31 ` Lars-Dominik Braun [this message]
2023-03-08 19:43 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-09 2:15 ` Cuirass package build timeouts and max-silent-time [was Re: Merging branch wip-haskell] Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZAjildvCQiotaBff@noor.fritz.box \
--to=lars@6xq.net \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.