all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: How to notice when my change breaks something
Date: Sun, 11 Feb 2018 17:35:43 -0500	[thread overview]
Message-ID: <87a7wfm9xc.fsf@netris.org> (raw)
In-Reply-To: <878tc0o0co.fsf_-_@gmail.com> (Chris Marusich's message of "Sun, 11 Feb 2018 01:07:19 +0100")

Hi Chris,

Chris Marusich <cmmarusich@gmail.com> writes:

> How do you notice when a change breaks something else?  You so
> frequently notice these things, it almost seems like you're omniscient!
>
> Do you have an automated mechanism for doing this, or are you manually
> checking things frequently?

I regularly check Hydra for newly failed packages.  To see the most
recent evaluations, visit <https://hydra.gnu.org/evals>.  Each
evaluation corresponds to a commit of Guix's git repo.  You can compare
two evaluations with URLs of the form
<https://hydra.gnu.org/eval/109907?compare=109906>, which will compare
evaluation 109907 to the previous evaluation 109906.  It is also often
useful to compare to a slightly older evaluation, especially one with an
unusually low number of failures, e.g.
<https://hydra.gnu.org/eval/109907?compare=109896> where 109896 was the
most recent evaluation of 'master' with fewer than 1900 failures.

Note that hydra.gnu.org is not sufficiently powerful for the work it is
currently doing, so it often takes on the order of several *minutes* for
the above URLs to load, and sometimes the Nginx front-end will time-out
before that happens.  Our new build farm is vastly more powerful, but
its web interface is currently quite rudimentary and not yet sufficient
for the kind of monitoring I do on Hydra.

Hope this helps.

       Mark

  reply	other threads:[~2018-02-11 22:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180208040203.20434.7928@vcs0.savannah.gnu.org>
     [not found] ` <20180208040204.6328E20AD1@vcs0.savannah.gnu.org>
2018-02-09  8:43   ` 02/05: gnu: luajit: Update to 2.1.0-beta3 Mark H Weaver
2018-02-11  0:07     ` How to notice when my change breaks something (was: Re: 02/05: gnu: luajit: Update to 2.1.0-beta3.) Chris Marusich
2018-02-11 22:35       ` Mark H Weaver [this message]
2018-02-18 18:30         ` How to notice when my change breaks something Chris Marusich
2018-02-18 21:04         ` Björn Höfling
2018-02-20  0:24     ` 02/05: gnu: luajit: Update to 2.1.0-beta3 Tobias Geerinckx-Rice

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=87a7wfm9xc.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@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 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.