From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: 01/01: gnu: gstreamer: Skip failing test on 32-bit systems. Date: Sun, 16 Jun 2019 17:31:08 -0400 Message-ID: <877e9lusir.fsf@netris.org> References: <20190613121214.23499.29535@vcs0.savannah.gnu.org> <20190613121215.EBF7320949@vcs0.savannah.gnu.org> <87imt95qtc.fsf@netris.org> <877e9m3qom.fsf@devup.no> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40797) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hccoo-0006ZO-Ln for guix-devel@gnu.org; Sun, 16 Jun 2019 17:36:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hccoi-00064k-MZ for guix-devel@gnu.org; Sun, 16 Jun 2019 17:36:03 -0400 Received: from world.peace.net ([64.112.178.59]:52032) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hccoe-0005kq-7N for guix-devel@gnu.org; Sun, 16 Jun 2019 17:35:59 -0400 In-Reply-To: <877e9m3qom.fsf@devup.no> (Marius Bakke's message of "Sun, 16 Jun 2019 10:00:41 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Marius Bakke Cc: guix-devel@gnu.org Hi Marius, Marius Bakke writes: > Mark H Weaver writes: > >> guix-commits@gnu.org writes: >> >>> mbakke pushed a commit to branch staging >>> in repository guix. >>> >>> commit 2a9d89afb6fb869dd2bdf1e9f710f487786930fc >>> Author: Marius Bakke >>> Date: Thu Jun 13 14:08:32 2019 +0200 >>> >>> gnu: gstreamer: Skip failing test on 32-bit systems. >>> >>> * gnu/packages/gstreamer.scm (gstreamer)[arguments]: When building for a >>> 32-bit system, add #:phases. >> [...] >>> + ,@(if (not (target-64bit?)) >>> + ;; Skip test that fails on 32-bit systems: >>> + ;; . >>> + `(#:phases (modify-phases %standard-phases >>> + (add-before 'check 'disable-gstbufferpool-test >>> + (lambda _ >>> + (substitute* "tests/check/Makefile" >>> + (("^[[:blank:]]+gst/gstbufferpool.*$") >>> + "")) >>> + #t)))) >>> + '()))) >> >> This might be sweeping a critical bug under the rug. Does >> >> Unexpected critical/warning: gst_buffer_resize_range: >> assertion 'bufmax >= bufoffs + offset + size' failed >> >> really sound like something we can safely ignore? > > I think you are right to be concerned. I found the upstream commit that > introduced the problem. See > . Thanks for checking. > Do you have a preference for reverting the faulty commits, or going back > to 1.14.5? It depends on the nature of the faulty commit, whether other later commits somehow depend on it, and whether other potential security holes were fixed since 1.14.5. Maybe use 1.14.5, possibly with cherry-picked fixes applied as patches? I'm not sure, and I don't have time to investigate right now, but I trust your judgement to choose the best available option. Thank you! Mark