unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: staging evaluation in progress
Date: Wed, 25 Apr 2018 10:32:43 -0400	[thread overview]
Message-ID: <8736zjtkz8.fsf@netris.org> (raw)
In-Reply-To: <20180425132135.GC17662@macbook41> (Efraim Flashner's message of "Wed, 25 Apr 2018 16:21:35 +0300")

Efraim Flashner <efraim@flashner.co.il> writes:

> On Mon, Apr 23, 2018 at 09:53:04PM -0400, Mark H Weaver wrote:
>> Marius Bakke <mbakke@fastmail.com> writes:
>> 
>> > Mark H Weaver <mhw@netris.org> writes:
>> >
>> >> Hi Marius,
>> >>
>> >> Marius Bakke <mbakke@fastmail.com> writes:
>> >>
>> >>> I just started a 'staging' evaluation:
>> >>>
>> >>> https://hydra.gnu.org/jobset/gnu/staging
>> >>>
>> >>> Fairly minor changes this round, highlights include Wayland 1.15 and
>> >>> GStreamer 1.14.  We narrowly missed Mesa 17.3.9 which was scheduled for
>> >>> today but delayed, hopefully 17.3.8 doesn't introduce any new bugs.
>> >>>
>> >>> Results should start ticking in tomorrow.
>> >>
>> >> The main issue I see so far is that 'gst-plugins-base' seems to
>> >> consistently fail the "elements/opus" test on i686-linux.  It failed
>> >> twice in a row, anyway:
>> >>
>> >>   https://hydra.gnu.org/build/2635798
>> >
>> > I can reproduce this failure locally, and could not find related bug
>> > reports or git commits upstream.  For now I downgraded to 1.12.5 so we
>> > can proceed, and will report the i686 and armhf issues upstream.
>> 
>> Instead of downgrading gstreamer, I think it would be better to simply
>> disable that test on i686 for now.  Most likely, it is due to tests that
>> are intolerant of the double rounding that occurs on i686 without SSE2,
>> where the old x87 FP instructions are used instead.  The double rounding
>> happens because x87 operations are performed on 80-bit double-extended
>> precision floating-point numbers, which must then be rounded a second
>> time when they are converted to 64-bit doubles as used in C.
>> 
>> What do you think?
>> 
>>       Mark
>> 
>
> somewhat random tests fail on aarch64 also, different ones from the
> other architectures. I'd suggest we wait it out until 1.14.1 and watch
> upstream for bug fixes.

Do we know if there are any security fixes in 1.14.0 that are not in
1.12.5?  Is the 1.12.x branch still receiving security updates?

       Mark

  reply	other threads:[~2018-04-25 14:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 16:36 staging evaluation in progress Marius Bakke
2018-04-18 21:23 ` Ludovic Courtès
2018-04-19 12:11 ` Mark H Weaver
2018-04-23 18:15   ` Marius Bakke
2018-04-24  1:53     ` Mark H Weaver
2018-04-25 13:21       ` Efraim Flashner
2018-04-25 14:32         ` Mark H Weaver [this message]
2018-04-26 10:34           ` Marius Bakke
2018-04-25 14:04       ` Marius Bakke
2018-04-26 13:53 ` Arun Isaac
2018-04-26 14:06   ` Marius Bakke
2018-04-26 18:48     ` Arun Isaac

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=8736zjtkz8.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    /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).