[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite.
|
From: |
Marius Bakke |
|
Subject: |
Re: 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite. |
|
Date: |
Sun, 07 Jan 2018 13:42:27 +0100 |
|
User-agent: |
Notmuch/0.25.3 (https://notmuchmail.org) Emacs/25.3.1 (x86_64-pc-linux-gnu) |
Chris Marusich <address@hidden> writes:
> Leo Famulari <address@hidden> writes:
>
>> On Wed, Dec 27, 2017 at 07:57:17PM -0500, Mark H Weaver wrote:
>>> Alas, your most recent changes seem to have now broken qgpgme:
>>>
>>> https://hydra.gnu.org/eval/109869#tabs-now-fail
>>> https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.x86_64-linux
>>> https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.i686-linux
>>> https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.armhf-linux
>>
>> Sigh... I didn't even know this package existed. I'll take a look.
>
> I'm not sure how to use Hydra... Is there a place in Hydra one can go
> after committing a change to know if it broke a package like this?
See <https://hydra.gnu.org/jobset/gnu/master>.
If you click on an evaluation, you'll find a tab listing the new "jobs"
(builds), and another listing existing jobs that now started to fail.
The latest btrfs-progs broke on i686 and armhf, as an example:
<https://hydra.gnu.org/eval/109880#tabs-new>.
signature.asc
Description: PGP signature