From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Luca Vizzarro <luca.vizzarro@arm.com>, zhoumin@loongson.cn
Subject: |WARNING| pw146554-146560 [PATCH v3 1/7] dts: rename build target to DPDK build
Date: Tue, 22 Oct 2024 10:56:31 +0800 [thread overview]
Message-ID: <202410220256.49M2uVp62032432@localhost.localdomain> (raw)
In-Reply-To: <20241021224627.1278175-2-luca.vizzarro@arm.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/146554
_apply patch failure_
Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Mon, 21 Oct 2024 23:46:21 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: cff6dba7ff8521df410b40399fd8aca5b450a05b
Apply patch set 146554-146560 failed:
Checking patch doc/guides/tools/dts.rst...
error: while searching for:
. code-block:: console
(dts-py3.10) $ ./main.py --help
usage: main.py [-h] [--config-file FILE_PATH] [--output-dir DIR_PATH] [-t SECONDS] [-v] [-s] (--tarball FILE_PATH | --revision ID)
[--compile-timeout SECONDS] [--test-suite TEST_SUITE [TEST_CASES ...]] [--re-run N_TIMES]
Run DPDK test suites. All options may be specified with the environment variables provided in brackets. Command line arguments have higher
priority.
options:
-h, --help show this help message and exit
--config-file FILE_PATH
[DTS_CFG_FILE] The configuration file that describes the test cases, SUTs and targets. (default: conf.yaml)
--output-dir DIR_PATH, --output DIR_PATH
[DTS_OUTPUT_DIR] Output directory where DTS logs and results are saved. (default: output)
-t SECONDS, --timeout SECONDS
[DTS_TIMEOUT] The default timeout for all DTS operations except for compiling DPDK. (default: 15)
-v, --verbose [DTS_VERBOSE] Specify to enable verbose output, logging all messages to the console. (default: False)
-s, --skip-setup [DTS_SKIP_SETUP] Specify to skip all setup steps on SUT and TG nodes. (default: False)
--tarball FILE_PATH, --snapshot FILE_PATH
[DTS_DPDK_TARBALL] Path to DPDK source code tarball to test. (default: None)
--revision ID, --rev ID, --git-ref ID
[DTS_DPDK_REVISION_ID] Git revision ID to test. Could be commit, tag, tree ID etc. To test local changes, first
commit them, then use their commit ID. (default: None)
--compile-timeout SECONDS
[DTS_COMPILE_TIMEOUT] The timeout for compiling DPDK. (default: 1200)
--test-suite TEST_SUITE [TEST_CASES ...]
[DTS_TEST_SUITES] A list containing a test suite with test cases. The first parameter is the test suite name, and
the rest are test case names, which are optional. May be specified multiple times. To specify multiple test suites
in the environment variable, join the lists with a comma. Examples: --test-suite suite case case --test-suite
suite case ... | DTS_TEST_SUITES='suite case case, suite case, ...' | --test-suite suite --test-suite suite case
... | DTS_TEST_SUITES='suite, suite case, ...' (default: [])
--re-run N_TIMES, --re_run N_TIMES
[DTS_RERUN] Re-run each test case the specified number of times if a test failure occurs. (default: 0)
--random-seed NUMBER [DTS_RANDOM_SEED] The seed to use with the pseudo-random generator. If not specified, the configuration value is
used instead. If that's also not specified, a random seed is generated. (default: None)
The brackets contain the names of environment variables that set the same thing.
The minimum DTS needs is a config file and a DPDK tarball or git ref ID.
You may pass those to DTS using the command line arguments or use the default paths.
Example command for running DTS with the template configuration and DPDK tag v23.11:
error: patch failed: doc/guides/tools/dts.rst:221
error: doc/guides/tools/dts.rst: patch does not apply
prev parent reply other threads:[~2024-10-22 3:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241021224627.1278175-2-luca.vizzarro@arm.com>
2024-10-21 22:16 ` qemudev
2024-10-21 22:48 ` |SUCCESS| pw146554 " checkpatch
2024-10-22 2:56 ` qemudev [this message]
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=202410220256.49M2uVp62032432@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=luca.vizzarro@arm.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).