From: Mark H Weaver <mhw@netris.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: End of beta soon? drop i686?
Date: Wed, 12 Dec 2018 12:52:32 -0500 [thread overview]
Message-ID: <87h8fiaays.fsf@netris.org> (raw)
In-Reply-To: <20181211212233.21106b5e@scratchpost.org> (Danny Milosavljevic's message of "Tue, 11 Dec 2018 21:22:33 +0100")
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> writes:
>> Note that we also lost 'icecat' on armhf-linux with the 52->60 upgrade,
>> because our 'rust' packages have never worked on armhf-linux.
>
> Wait, what? I wasn't aware. Let's track this as a bug - that's
> definitely not supposed to happen.
>
> mrustc works on armhf - I tested it on physical armhf hardware before merging.
>
> So one of the other Rusts doesn't work? I'll check out Hydra logs...
>
> https://hydra.gnu.org/build/3215481/nixlog/1/raw indicates a timeout of
> silence - we might want to increase it. (this particular step takes many
> many MANY minutes on x86_64, too).
>
> Would that be the "(properties '((timeout . 3600)))))" thing? Or is a
> "timeout of silence" an extra setting?
I see that you increased the timeouts for rust-1.19.0, and I asked Hydra
to retry the build. It failed again, in a different way:
https://hydra.gnu.org/build/3215481/nixlog/2/raw
Mark
next prev parent reply other threads:[~2018-12-12 17:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 7:58 End of beta soon? drop i686? swedebugia
2018-12-11 9:19 ` ng0
2018-12-12 2:15 ` Ricardo Wurmus
2018-12-12 9:33 ` ng0
2018-12-11 20:02 ` Mark H Weaver
2018-12-11 20:22 ` Danny Milosavljevic
2018-12-11 23:14 ` Mark H Weaver
2018-12-12 17:52 ` Mark H Weaver [this message]
2018-12-12 2:16 ` Ricardo Wurmus
2018-12-12 7:40 ` Andreas Enge
2018-12-13 12:26 ` swedebugia
2018-12-12 16:19 ` Joshua Branson
2018-12-12 23:27 ` Mark H Weaver
2018-12-12 22:33 ` George Clemmer
-- strict thread matches above, loose matches on Subject: below --
2018-12-12 17:52 Mark H Weaver
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8fiaays.fsf@netris.org \
--to=mhw@netris.org \
--cc=dannym@scratchpost.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).