“guile-next” failed — but actually didn’t

“guile-next” failed — but actually didn’t

[Ricardo Wurmus]

Hi Guix,

Hydra lists the build for “guile-next” at version 2.1.4 as failed, even
though, according to the logs, it has been built successfully.  This
causes the “guile2.2-*” packages to be marked as failed, too.

See https://hydra.gnu.org/build/1473033

What’s going on there?  Should we restart the build or can we mark it as
successful somehow?

~~ Ricardo

Re: “guile-next” failed — but actually didn’t

[Alex Vong]

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

Hi,

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi Guix,
>
> Hydra lists the build for “guile-next” at version 2.1.4 as failed, even
> though, according to the logs, it has been built successfully.  This
> causes the “guile2.2-*” packages to be marked as failed, too.
>
> See https://hydra.gnu.org/build/1473033
>
> What’s going on there?  Should we restart the build or can we mark it as
> successful somehow?
>
The status is now "Success" on <https://hydra.gnu.org/build/1473033>.

> ~~ Ricardo

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

Re: “guile-next” failed — but actually didn’t

[Ludovic Courtès]

Hi,

Alex Vong <alexvong1995@gmail.com> skribis:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Hi Guix,
>>
>> Hydra lists the build for “guile-next” at version 2.1.4 as failed, even
>> though, according to the logs, it has been built successfully.  This
>> causes the “guile2.2-*” packages to be marked as failed, too.
>>
>> See https://hydra.gnu.org/build/1473033
>>
>> What’s going on there?  Should we restart the build or can we mark it as
>> successful somehow?

That can happen when, say, the SSH connection to the build machine fails
before the result has been retrieved on hydra.gnu.org (dunno if that is
the case here.)

> The status is now "Success" on <https://hydra.gnu.org/build/1473033>.

Presumably somebody restarted it in the meantime.  :-)

Ludo’.