From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, Honnappa.Nagarahalli@arm.com,
jspewock@iol.unh.edu, probb@iol.unh.edu, paul.szczepanek@arm.com,
Luca.Vizzarro@arm.com, npratte@iol.unh.edu
Cc: dev@dpdk.org, "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [PATCH v1 1/4] dts: add tg node execution setup and teardown
Date: Tue, 23 Apr 2024 11:12:49 +0200 [thread overview]
Message-ID: <20240423091252.62924-2-juraj.linkes@pantheon.tech> (raw)
In-Reply-To: <20240423091252.62924-1-juraj.linkes@pantheon.tech>
The setup and teardown for the execution stage was meant to be run on
the tg node too, but was mistakenly omitted.
Fixes: cecfe0aabf58 ("dts: add traffic generator abstractions")
Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
---
dts/framework/runner.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/dts/framework/runner.py b/dts/framework/runner.py
index db8e3ba96b..2f25a3e941 100644
--- a/dts/framework/runner.py
+++ b/dts/framework/runner.py
@@ -422,6 +422,7 @@ def _run_execution(
execution_result.add_sut_info(sut_node.node_info)
try:
sut_node.set_up_execution(execution)
+ tg_node.set_up_execution(execution)
execution_result.update_setup(Result.PASS)
except Exception as e:
self._logger.exception("Execution setup failed.")
@@ -438,6 +439,7 @@ def _run_execution(
try:
self._logger.set_stage(DtsStage.execution_teardown)
sut_node.tear_down_execution()
+ tg_node.tear_down_execution()
execution_result.update_teardown(Result.PASS)
except Exception as e:
self._logger.exception("Execution teardown failed.")
--
2.34.1
next prev parent reply other threads:[~2024-04-23 9:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 9:12 [PATCH v1 0/4] node and inheritance improvements Juraj Linkeš
2024-04-23 9:12 ` Juraj Linkeš [this message]
2024-04-23 9:18 ` [PATCH v1 1/4] dts: add tg node execution setup and teardown Luca Vizzarro
2024-04-30 16:15 ` Jeremy Spewock
2024-04-23 9:12 ` [PATCH v1 2/4] dts: unify class inheritance from object Juraj Linkeš
2024-04-23 9:19 ` Luca Vizzarro
2024-04-23 14:53 ` Patrick Robb
2024-04-30 16:15 ` Jeremy Spewock
2024-04-23 9:12 ` [PATCH v1 3/4] dts: unify super calls Juraj Linkeš
2024-04-23 10:06 ` Luca Vizzarro
2024-04-23 14:57 ` Patrick Robb
2024-04-30 16:15 ` Jeremy Spewock
2024-04-23 9:12 ` [PATCH v1 4/4] dts: refine pre-test setup and teardown steps Juraj Linkeš
2024-04-23 9:19 ` Luca Vizzarro
2024-04-30 16:15 ` Jeremy Spewock
2024-04-23 10:07 ` [PATCH v1 0/4] node and inheritance improvements Luca Vizzarro
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=20240423091252.62924-2-juraj.linkes@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Luca.Vizzarro@arm.com \
--cc=dev@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=npratte@iol.unh.edu \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
/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).