unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Felix Lechner <felix.lechner@lease-up.com>,
	Simon Tournier <zimon.toutoune@gmail.com>,
	guix-devel@gnu.org, Mathieu Othacehe <othacehe@gnu.org>
Subject: Cuirass package build timeouts and max-silent-time [was Re: Merging branch wip-haskell]
Date: Wed, 8 Mar 2023 21:15:29 -0500	[thread overview]
Message-ID: <ZAlBQUEwSXDjct+a@jasmine.lan> (raw)
In-Reply-To: <ZAjildvCQiotaBff@noor.fritz.box>

On Wed, Mar 08, 2023 at 08:31:33PM +0100, Lars-Dominik Braun wrote:
> 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.

I suspect that GHC was never built by Cuirass, but that somebody logged
in to the build server and invoked `guix build ghc
--max-silent-time=99999`.

There's no logs of a successful build of GHC 9.2.5 available through the
Cuirass web interface, which is a clue that my hunch is correct. Builds
performed "by hand" don't appear in the web interface.

https://ci.guix.gnu.org/search?query=spec%3Amaster+ghc-9.2.5

Are we sure that Cuirass honors the max-silent-time property? If I
remember correctly, it did not do so in the past.


      parent reply	other threads:[~2023-03-09  2:16 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
2023-03-08 19:43           ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-09  2:15           ` Leo Famulari [this message]

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=ZAlBQUEwSXDjct+a@jasmine.lan \
    --to=leo@famulari.name \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=lars@6xq.net \
    --cc=othacehe@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 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).