From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 2/3] lib: Add support for TDEBUG tst_res() flag
Date: Thu, 14 Dec 2023 00:48:27 +0100 [thread overview]
Message-ID: <20231213234827.GC774490@pevik> (raw)
In-Reply-To: <ZXoC6LUE8ePDPRIU@rei>
Hi all,
...
> > + {"v", "-v Prints debug information"},
> Maybe this should now be called -d since we call it TDEBUG and that will
> avoid having a bit confusing parameters with both -v and -V used.
Also, I have forgotten, I would prefer to enable TDEBUG messages also via
environment variable (e.g. TST_ENABLE_DEBUG). This will be easier for openQA and
possibly other testing frameworks to rerun runtest with debug info (-d is enough
to run locally, but it would require to change runtest to add it to particular
test, but exporting variable will work on unmodified sources).
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-12-13 23:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 16:18 [LTP] [PATCH v3 0/3] Add TDEBUG tst_res() flag Petr Vorel
2023-12-11 16:18 ` [LTP] [PATCH v3 1/3] lib/tests: Add test for testing tst_res() flags Petr Vorel
2023-12-13 19:04 ` Cyril Hrubis
2023-12-13 23:40 ` Petr Vorel
2023-12-14 9:09 ` Cyril Hrubis
2023-12-14 12:19 ` Petr Vorel
2023-12-14 12:26 ` Petr Vorel
2023-12-11 16:18 ` [LTP] [PATCH v3 2/3] lib: Add support for TDEBUG tst_res() flag Petr Vorel
2023-12-13 19:15 ` Cyril Hrubis
2023-12-13 23:11 ` Petr Vorel
2023-12-14 9:41 ` Cyril Hrubis
2023-12-14 12:08 ` Petr Vorel
2023-12-13 23:48 ` Petr Vorel [this message]
2023-12-14 9:39 ` Cyril Hrubis
2023-12-11 16:18 ` [LTP] [PATCH v3 3/3] fsx-linux: Reduce log output with TDEBUG Petr Vorel
2023-12-12 10:08 ` Andrea Cervesato via ltp
2023-12-13 19:18 ` Cyril Hrubis
2023-12-11 16:27 ` [LTP] [PATCH v3 0/3] Add TDEBUG tst_res() flag Jan Stancek
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231213234827.GC774490@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.