Re: 02/05: gnu: luajit: Update to 2.1.0-beta3.

Re: 02/05: gnu: luajit: Update to 2.1.0-beta3.

[Mark H Weaver]

Hi Tobias,

me@tobias.gr (Tobias Geerinckx-Rice) writes:

> nckx pushed a commit to branch master
> in repository guix.
>
> commit 906f1b48e20a032c22a164c89f9e8862ab2bec7a
> Author: Tobias Geerinckx-Rice <me@tobias.gr>
> Date:   Wed Jan 3 09:01:53 2018 +0100
>
>     gnu: luajit: Update to 2.1.0-beta3.
>     
>     * gnu/packages/lua.scm (luajit): Update to 2.1.0-beta3.
>     [source]: Remove symlinks patch.
>     * gnu/packages/patches/luajit-symlinks.patch: Delete file.
>     * gnu/local.mk (dist_patch_DATA): Remove it.

This seems to have broken the 'love' package, which uses luajit.

  https://hydra.gnu.org/build/2488685

Would you be willing to investigate?

       Mark

How to notice when my change breaks something (was: Re: 02/05: gnu: luajit: Update to 2.1.0-beta3.)

[Chris Marusich]

[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]

Hi Mark,

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?  We should all be able to do this, but I
suspect some people (myself included) are not sure how to do it.  If you
could share any tips, that'd be really nice.

Here's an example of what I mean:

Mark H Weaver <mhw@netris.org> writes:

> Hi Tobias,
>
> me@tobias.gr (Tobias Geerinckx-Rice) writes:
>
>> nckx pushed a commit to branch master
>> in repository guix.
>>
>> commit 906f1b48e20a032c22a164c89f9e8862ab2bec7a
>> Author: Tobias Geerinckx-Rice <me@tobias.gr>
>> Date:   Wed Jan 3 09:01:53 2018 +0100
>>
>>     gnu: luajit: Update to 2.1.0-beta3.
>>     
>>     * gnu/packages/lua.scm (luajit): Update to 2.1.0-beta3.
>>     [source]: Remove symlinks patch.
>>     * gnu/packages/patches/luajit-symlinks.patch: Delete file.
>>     * gnu/local.mk (dist_patch_DATA): Remove it.
>
> This seems to have broken the 'love' package, which uses luajit.
>
>   https://hydra.gnu.org/build/2488685
>
> Would you be willing to investigate?
>
>        Mark
>

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: How to notice when my change breaks something

[Mark H Weaver]

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

Re: How to notice when my change breaks something

[Chris Marusich]

[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]

Mark H Weaver <mhw@netris.org> writes:

> 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.

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.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: How to notice when my change breaks something

[Björn Höfling]

Hi Mark,

On Sun, 11 Feb 2018 17:35:43 -0500
Mark H Weaver <mhw@netris.org> wrote:

> 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


Yes, that definitely helped me too.

I have a follow-up question: This day I realized that teeworlds broke
on core-updates due to a freetype update (see
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30518).

Now I thought: Is it possible to download the whole list of
(directly) breaking packages from Hydra? If so, I could fold-packages
through them and filter out those that also have freetype as a
dependency and probably fix them with a one-liner. Is there any
download/API functionality for Hydra?

Björn

Re: 02/05: gnu: luajit: Update to 2.1.0-beta3.

[Tobias Geerinckx-Rice]

Mark,

On Fri, 2018-02-09 at 03:43 -0500, Mark H Weaver wrote:
> > nckx pushed a commit to branch master
> > in repository guix.
> > 
> > commit 906f1b48e20a032c22a164c89f9e8862ab2bec7a
> > Author: Tobias Geerinckx-Rice <me@tobias.gr>
> > Date:   Wed Jan 3 09:01:53 2018 +0100
> > 
> >     gnu: luajit: Update to 2.1.0-beta3.
> >     
> >     * gnu/packages/lua.scm (luajit): Update to 2.1.0-beta3.
> >     [source]: Remove symlinks patch.
> >     * gnu/packages/patches/luajit-symlinks.patch: Delete file.
> >     * gnu/local.mk (dist_patch_DATA): Remove it.
> 
> This seems to have broken the 'love' package, which uses luajit.
> 
>   https://hydra.gnu.org/build/2488685
> 
> Would you be willing to investigate?

Sure! It'll take me a while to download the i686 dependencies but I'll
take a look. 

Sorry for the late reply, I've had very limited e-mail access the past
few weeks.

Kind regards,

T G-R