From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: mingjinx.ye@intel.com, robot@bytheb.org
Subject: |FAILURE| pw134153 [PATCH v6] app/test: secondary process passes allow parameters
Date: Mon, 13 Nov 2023 06:59:42 -0500 [thread overview]
Message-ID: <20231113115942.121006-1-robot@bytheb.org> (raw)
In-Reply-To: <20231113104222.85891-1-mingjinx.ye@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/134153/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/6849256808
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-debug+doc+examples+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-debug+doc+examples+tests" at step Build and test
####################################################################################
101/110 DPDK:fast-tests / telemetry_json_autotest OK 0.22 s
102/110 DPDK:fast-tests / thash_autotest OK 0.27 s
103/110 DPDK:fast-tests / threads_autotest OK 0.37 s
104/110 DPDK:fast-tests / ticketlock_autotest OK 0.27 s
105/110 DPDK:fast-tests / timer_autotest OK 2.82 s
106/110 DPDK:fast-tests / trace_autotest OK 0.22 s
107/110 DPDK:fast-tests / trace_autotest_with_traces OK 0.22 s
108/110 DPDK:fast-tests / vdev_autotest OK 0.22 s
109/110 DPDK:fast-tests / version_autotest OK 0.22 s
110/110 DPDK:fast-tests / telemetry_all OK 1.07 s
Ok: 91
Expected Fail: 0
Fail: 13
Unexpected Pass: 0
Skipped: 6
Timeout: 0
Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-11-13 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231113104222.85891-1-mingjinx.ye@intel.com>
2023-11-13 10:46 ` |SUCCESS| " qemudev
2023-11-13 10:50 ` qemudev
2023-11-13 10:57 ` checkpatch
2023-11-13 11:59 ` 0-day Robot [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=20231113115942.121006-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=mingjinx.ye@intel.com \
--cc=test-report@dpdk.org \
/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).