From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:55963) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hmfv1-00055K-Ax for guix-patches@gnu.org; Sun, 14 Jul 2019 10:56:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hmfv0-0006kM-Bk for guix-patches@gnu.org; Sun, 14 Jul 2019 10:56:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:36796) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hmfv0-0006ik-7W for guix-patches@gnu.org; Sun, 14 Jul 2019 10:56:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hmfv0-0005R4-38 for guix-patches@gnu.org; Sun, 14 Jul 2019 10:56:02 -0400 Subject: [bug#36258] [PATCH 1/2] gnu: monero: Update to 0.14.1.0. Resent-Message-ID: References: <20190617084436.12311-1-glv@posteo.net> <49b66acb-c2f9-5fd0-97aa-16711ae933e1@riseup.net> <87imsx2rk3.fsf@yamatai> <87blyobgzl.fsf@yamatai> <9abcc53c-1a07-d3b3-2b9f-1571328c7414@riseup.net> <87y31rtijx.fsf@yamatai> <87mui63rnd.fsf@yamatai> <11d7747e-a7c8-3f29-dd8a-7dc1534dfc23@riseup.net> <871rz74eli.fsf@gnu.org> <11a6e577-7cde-0be1-acf2-9f2ab13145ed@riseup.net> <87pnmcltpn.fsf@yamatai> <87tvbo68tb.fsf@gnu.org> From: swedebugia Message-ID: Date: Sun, 14 Jul 2019 16:55:27 +0200 MIME-Version: 1.0 In-Reply-To: <87tvbo68tb.fsf@gnu.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= , Guillaume Le Vaillant Cc: 36258-done@debbugs.gnu.org On 2019-07-14 15:32, Ludovic Courtès wrote: ... > > I’d rather not disable tests just because they take a long time. > > An obvious workaround would be to have the test machinery display some > sort of progress report or really anything that shows it’s still “doing > something” so that we don’t hit max-silent-timeout. > > Do you know if the build system or CTest has a flag that would make it > more verbose? It has: https://linux.die.net/man/1/ctest -V,--verbose Enable verbose output from tests. Test output is normally suppressed and only summary information is displayed. This option will show all test output. -VV,--extra-verbose Enable more verbose output from tests. Test output is normally suppressed and only summary information is displayed. This option will show even more test output. --debug Displaying more verbose internals of CTest. This feature will result in large number of output that is mostly useful for debugging dashboard problems. Could you test those Guillaume and see if it helps us? -- Cheers Swedebugia