From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: How to notice when my change breaks something Date: Sun, 18 Feb 2018 19:30:56 +0100 Message-ID: <87wozaduan.fsf@gmail.com> References: <20180208040203.20434.7928@vcs0.savannah.gnu.org> <20180208040204.6328E20AD1@vcs0.savannah.gnu.org> <87vaf6d04i.fsf@netris.org> <878tc0o0co.fsf_-_@gmail.com> <87a7wfm9xc.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36416) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1enTjw-0003iw-Mc for guix-devel@gnu.org; Sun, 18 Feb 2018 13:31:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1enTjr-0003NC-Pe for guix-devel@gnu.org; Sun, 18 Feb 2018 13:31:08 -0500 Received: from mail-pl0-x22f.google.com ([2607:f8b0:400e:c01::22f]:39585) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1enTjr-0003Mq-JD for guix-devel@gnu.org; Sun, 18 Feb 2018 13:31:03 -0500 Received: by mail-pl0-x22f.google.com with SMTP id s13so4466961plq.6 for ; Sun, 18 Feb 2018 10:31:03 -0800 (PST) In-Reply-To: <87a7wfm9xc.fsf@netris.org> (Mark H. Weaver's message of "Sun, 11 Feb 2018 17:35:43 -0500") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Mark H Weaver Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Mark H Weaver writes: > Hi Chris, > > Chris Marusich 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 . Each > evaluation corresponds to a commit of Guix's git repo. You can compare > two evaluations with URLs of the form > , 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. > 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. Yes, it does! Thank you for the information. I'll try to watch Hydra a little more, especially after pushing changes, and hopefully these instructions will encourage others to do the same. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlqJxmAACgkQ3UCaFdgi Rp26mRAAs6cDOucMLw0U56Ve2Se2jW3jma1e2CGUqSFmwGHzviYHGKpfyb5V59fZ 4cEHafF8SG3POiR3ul843PPd2xvEg1ZlT++eRteJbe5osbEP37zJe0/sMsjvrwT7 1UhEyXJzKFkMeXhpzXdMQJCdVTPbfwdgG3zC7d0PI4yU90RDbc+oewKFv3bc8aeU bjRr4iAMIuUfrRM7ITYukAToVlhoRjJjx8PBVC/UjiK2uwpFmf4qT0VKzQlGu1DO PZ9xftdS9C/t0tbRYaveMqjTif5ypOBGLzqU7OrRbDOrnyOvzB+GuyLeq7y2pRpX Qt0tErBWFx2XV4y/S/CGMlGAKg5yBFFm6ppjQ6YwgN+fS5/9GIRVua5hy6ui+7QY 0zqWwdrZU1nL61V+oF/9Zv3kr2wbKZHVjiZwGipFyaSTCRC2KNJ9/34M4mxSKPT3 1PIbW9rURqtgeymgRFrTk48wKox4Psu0nc78+lVGcdrUzqLuGqqI3qn4Ewvulkqw B3rdtABpsn2m33BNA73dLmFQWhsZ07seQRyF2wNhlB1tdKrQZWWfiZonjLJqZ7dm iKoQp2kJxdEvajAaWrpkzNFWNoi5Ai2wFOb7gSm6p/G3KboTvQl9aqzYPq8BC6CS LeBZfjejJn9ObYFRH+G01Ei0Wkm6ShahAzOOl3Dio0M6NW4VTCs= =3oKE -----END PGP SIGNATURE----- --=-=-=--