From: swedebugia <swedebugia@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Guillaume Le Vaillant" <glv@posteo.net>
Cc: 36258-done@debbugs.gnu.org
Subject: [bug#36258] [PATCH 1/2] gnu: monero: Update to 0.14.1.0.
Date: Sun, 14 Jul 2019 16:55:27 +0200 [thread overview]
Message-ID: <d0f6c277-8fdf-85dc-262a-e0764a861fbf@riseup.net> (raw)
In-Reply-To: <87tvbo68tb.fsf@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
next prev parent reply other threads:[~2019-07-14 14:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 8:44 [bug#36258] [PATCH 1/2] gnu: monero: Update to 0.14.1.0 Guillaume LE VAILLANT
2019-06-17 8:44 ` [bug#36259] [PATCH 2/2] gnu: monero-gui: " Guillaume LE VAILLANT
2019-06-26 12:08 ` Guillaume LE VAILLANT
2019-06-26 22:55 ` swedebugia
2019-07-03 10:07 ` bug#36259: " Ludovic Courtès
2019-06-22 20:38 ` [bug#36258] [PATCH 1/2] gnu: monero: " swedebugia
2019-06-22 22:17 ` Guillaume LE VAILLANT
2019-06-23 11:31 ` swedebugia
2019-06-23 12:53 ` Guillaume LE VAILLANT
2019-06-23 13:18 ` swedebugia
2019-06-24 6:20 ` swedebugia
2019-06-24 9:54 ` Guillaume LE VAILLANT
2019-06-25 10:07 ` Guillaume LE VAILLANT
2019-06-25 11:32 ` swedebugia
2019-07-03 10:06 ` bug#36258: " Ludovic Courtès
2019-07-14 11:11 ` [bug#36258] " swedebugia
2019-07-14 11:51 ` Guillaume Le Vaillant
2019-07-14 13:32 ` Ludovic Courtès
2019-07-14 14:55 ` swedebugia [this message]
2019-07-14 16:13 ` Guillaume Le Vaillant
2019-07-15 10:50 ` Ludovic Courtès
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=d0f6c277-8fdf-85dc-262a-e0764a861fbf@riseup.net \
--to=swedebugia@riseup.net \
--cc=36258-done@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=ludo@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).