From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7BE514399C; Mon, 22 Jan 2024 19:26:35 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 48EB2402C3; Mon, 22 Jan 2024 19:26:35 +0100 (CET) Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by mails.dpdk.org (Postfix) with ESMTP id F2ECD40298 for <dev@dpdk.org>; Mon, 22 Jan 2024 19:26:33 +0100 (CET) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 781561FB; Mon, 22 Jan 2024 10:27:19 -0800 (PST) Received: from localhost.localdomain (unknown [10.57.90.210]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id AF5753F762; Mon, 22 Jan 2024 10:26:32 -0800 (PST) From: Luca Vizzarro <luca.vizzarro@arm.com> To: dev@dpdk.org Cc: Luca Vizzarro <luca.vizzarro@arm.com>, =?UTF-8?q?Juraj=20Linke=C5=A1?= <juraj.linkes@pantheon.tech>, Paul Szczepanek <paul.szczepanek@arm.com> Subject: [PATCH 0/4] dts: error and usage improvements Date: Mon, 22 Jan 2024 18:26:07 +0000 Message-Id: <20240122182611.1904974-1-luca.vizzarro@arm.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org As mentioned in my previous DTS docs improvement patch series, here are some usage improvements to DTS. The main purpose is to give the first-time user of DTS some more meaningful messages of its usage. Secondly, report back stderr to the user when remote commands fail. For example, if DTS tries to run any program which is not installed on the target node, it will just say that it failed with its return code. The only way to see the actual error message is through the DEBUG level of verbosity. Rightfully though, errors should be logged as ERROR. Best, Luca Luca Vizzarro (4): dts: constrain DPDK source flag dts: customise argparse error message dts: show help when DTS is ran without args dts: log stderr with failed remote commands doc/guides/tools/dts.rst | 8 +- dts/framework/exception.py | 10 ++- .../remote_session/remote_session.py | 2 +- dts/framework/settings.py | 83 ++++++++++++++----- dts/framework/utils.py | 43 ++++++---- 5 files changed, 104 insertions(+), 42 deletions(-) -- 2.34.1