automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: amitprakashs@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw122697 [PATCH v3] eventdev: add trace points
Date: Mon, 30 Jan 2023 13:19:28 -0500	[thread overview]
Message-ID: <20230130181928.1900087-1-robot@bytheb.org> (raw)
In-Reply-To: <20230130173006.1724832-1-amitprakashs@marvell.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/122697/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4046591248
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+doc+tests" failed at step Build and test
"ubuntu-20.04-clang-asan+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+doc+tests" at step Build and test
####################################################################################
 95/104 DPDK:fast-tests / telemetry_data_autotest  OK       0.17 s 
 96/104 DPDK:fast-tests / table_autotest        OK       6.38 s 
 97/104 DPDK:fast-tests / ring_pmd_autotest     OK       0.17 s 
 98/104 DPDK:fast-tests / event_eth_tx_adapter_autotest  FAIL     0.22 s (killed by signal 11 SIGSEGV)
 99/104 DPDK:fast-tests / bitratestats_autotest  OK       0.17 s 
100/104 DPDK:fast-tests / latencystats_autotest  OK       0.17 s 
101/104 DPDK:fast-tests / pdump_autotest        OK       5.23 s 
102/104 DPDK:fast-tests / vdev_autotest         OK       0.17 s 
103/104 DPDK:fast-tests / compressdev_autotest  SKIP     0.17 s 
104/104 DPDK:fast-tests / telemetry_all         OK       8.79 s 

Ok:                   94
Expected Fail:         0
Fail:                  2
Unexpected Pass:       0
Skipped:               8
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-abi+doc+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-20.04-clang-asan+doc+tests" at step Build and test
####################################################################################
81/90 DPDK:fast-tests / telemetry_json_autotest  OK       0.27 s 
82/90 DPDK:fast-tests / telemetry_data_autotest  OK       0.27 s 
83/90 DPDK:fast-tests / table_autotest        OK      14.67 s 
84/90 DPDK:fast-tests / ring_pmd_autotest     OK       0.27 s 
85/90 DPDK:fast-tests / event_eth_tx_adapter_autotest  FAIL     0.97 s (exit status 1)
86/90 DPDK:fast-tests / bitratestats_autotest  OK       0.27 s 
87/90 DPDK:fast-tests / latencystats_autotest  OK       0.27 s 
88/90 DPDK:fast-tests / vdev_autotest         OK       0.27 s 
89/90 DPDK:fast-tests / compressdev_autotest  SKIP     0.27 s 
90/90 DPDK:fast-tests / telemetry_all         OK      10.70 s 

Ok:                   80
Expected Fail:         0
Fail:                  2
Unexpected Pass:       0
Skipped:               8
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-clang-asan+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2023-01-30 18:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230130173006.1724832-1-amitprakashs@marvell.com>
2023-01-30 17:23 ` |SUCCESS| " qemudev
2023-01-30 17:27 ` |FAILURE| " qemudev
2023-01-30 17:31 ` |SUCCESS| " checkpatch
2023-01-30 18:19 ` 0-day Robot [this message]
2023-02-03  8:33 ` qemudev
2023-02-03  8:37 ` |FAILURE| " qemudev
2023-01-30 18:02 |FAILURE| pw122697 [PATCH] [v3] " dpdklab
2023-01-30 18:02 dpdklab
2023-01-30 18:17 dpdklab
2023-01-30 22:23 dpdklab
2023-01-30 22:24 dpdklab
2023-01-30 22:25 dpdklab
2023-01-30 22:26 dpdklab
2023-01-30 22:26 dpdklab
2023-01-30 22:26 dpdklab
2023-01-30 22:26 dpdklab
2023-01-30 22:26 dpdklab
2023-01-30 22:27 dpdklab
2023-01-30 22:58 dpdklab

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=20230130181928.1900087-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=amitprakashs@marvell.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).