From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#31720: java-bouncycastle: tests fail and freeze Date: Fri, 15 Jun 2018 13:29:38 +0200 Message-ID: <878t7guw2l.fsf@elephly.net> References: <87602x1p5i.fsf@mdc-berlin.de> <8580f9f5a2c701bf8de0b08f43c36e59@lepiller.eu> <87r2llz4t6.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46951) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fTmvg-0003q2-0L for bug-guix@gnu.org; Fri, 15 Jun 2018 07:30:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fTmvb-0002Ep-28 for bug-guix@gnu.org; Fri, 15 Jun 2018 07:30:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:41112) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fTmva-0002Eb-UQ for bug-guix@gnu.org; Fri, 15 Jun 2018 07:30:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fTmva-0000Ha-M6 for bug-guix@gnu.org; Fri, 15 Jun 2018 07:30:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87r2llz4t6.fsf@elephly.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Julien Lepiller Cc: 31720@debbugs.gnu.org Ricardo Wurmus writes: > Julien Lepiller writes: > >> Le 2018-06-05 12:52, Ricardo Wurmus a =C3=A9crit: >>> The package java-bouncycastle has a failing test suite on core-updates. >>> After the first test fails there is no more progress and the build >>> eventually times out. >>> >>> I have disabled the test suite for now, but we should try to fix this. >>> >>> The failing test is =E2=80=9Corg.bouncycastle.mail.smime.test.AllTests= =E2=80=9D. >>> >>> -- >>> Ricardo >> >> I've observed this behavior on master: the test fails, build hangs for >> some very long time and then resumes and completes. I'm not sure why >> there is a failure and how not to run this specific test though. > > Yes, you are right. The check phase does succeed after a very long > time. I think the bigger problem here is that we are running tests but silently ignore test failures. This happens since the change to ignore return values of build phases, because the ant-build-system only returns #f on a test failure when it should raise an exception instead. -- Ricardo