From: Marcel Hamer via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] [lttng-tools] Removal of root_regression tests
Date: Mon, 13 Jun 2022 13:49:39 +0200 [thread overview]
Message-ID: <20220613114939.GA276938@windriver.com> (raw)
Hello,
Since version v2.12.9 of lttng-tools the root_regression file has been emptied
to make the tests part of the 'make check' sequence instead.
We were always actively using that test file as part of our regression testing.
In our case we are working in a cross-compilation environment, where the run.sh
script was used on target for testing and as such not at compile time. It is not
easy to run a make check sequence on a target.
It is now also a bit unclear which tests actually require root access and which
tests do not. I understood this was the reason the file was called
'root_regression'?
Some questions that get raised because of this:
- Is there now an alternative way to run regressions on target in case of a
cross-compilation environment?
- Would there be a possibility to fill the 'root_regression' file again and
possibly revert this change?
- How are tests now identified that require root access?
This has been as part of commit 9e2d9d2bae015e6748ebf8575ea602ee0fe65c62 in
lttng-tools.
Thank you in advance!
Kind regards,
Marcel
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2022-06-13 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 11:49 Marcel Hamer via lttng-dev [this message]
2022-06-13 15:21 ` [lttng-dev] [lttng-tools] Removal of root_regression tests Jonathan Rajotte-Julien via lttng-dev
2022-06-14 15:26 ` Marcel Hamer via lttng-dev
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=20220613114939.GA276938@windriver.com \
--to=lttng-dev@lists.lttng.org \
--cc=marcel.hamer@windriver.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 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 NNTP newsgroup(s).