From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com, robot@bytheb.org
Subject: |FAILURE| pw150198 [PATCH v2] test: improve resiliency of malloc autotest
Date: Fri, 17 Jan 2025 09:44:31 -0500 [thread overview]
Message-ID: <20250117144431.3353337-1-robot@bytheb.org> (raw)
In-Reply-To: <20250117135239.1980838-1-bruce.richardson@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/150198/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/12830618475
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
111/119 DPDK:fast-tests / thash_autotest OK 0.29s
112/119 DPDK:fast-tests / threads_autotest OK 0.38s
113/119 DPDK:fast-tests / ticketlock_autotest OK 0.27s
114/119 DPDK:fast-tests / timer_autotest OK 2.83s
115/119 DPDK:fast-tests / trace_autotest OK 0.25s
116/119 DPDK:fast-tests / trace_autotest_with_traces OK 0.26s
117/119 DPDK:fast-tests / vdev_autotest OK 0.24s
118/119 DPDK:fast-tests / version_autotest OK 0.24s
119/119 DPDK:fast-tests / telemetry_all OK 1.06s
Ok: 112
Expected Fail: 0
Fail: 1
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-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2025-01-17 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250117135239.1980838-1-bruce.richardson@intel.com>
2025-01-17 13:21 ` |SUCCESS| " qemudev
2025-01-17 13:25 ` |FAILURE| " qemudev
2025-01-17 13:53 ` |SUCCESS| " checkpatch
2025-01-17 14:44 ` 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=20250117144431.3353337-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=bruce.richardson@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).