automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: joshwash@google.com, robot@bytheb.org
Subject: |FAILURE| pw141135 [PATCH] net/gve: change QPLs to be queue resources
Date: Thu, 13 Jun 2024 20:04:39 -0400	[thread overview]
Message-ID: <20240614000439.3926472-1-robot@bytheb.org> (raw)
In-Reply-To: <20240613225953.610732-1-joshwash@google.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9508109986
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
####################################################################################
102/111 DPDK:fast-tests / telemetry_json_autotest  OK       0.27 s 
103/111 DPDK:fast-tests / thash_autotest        OK       0.27 s 
104/111 DPDK:fast-tests / threads_autotest      OK       0.37 s 
105/111 DPDK:fast-tests / ticketlock_autotest   OK       0.27 s 
106/111 DPDK:fast-tests / timer_autotest        OK       2.87 s 
107/111 DPDK:fast-tests / trace_autotest        OK       0.27 s 
108/111 DPDK:fast-tests / trace_autotest_with_traces  OK       0.27 s 
109/111 DPDK:fast-tests / vdev_autotest         OK       0.27 s 
110/111 DPDK:fast-tests / version_autotest      OK       0.27 s 
111/111 DPDK:fast-tests / telemetry_all         OK       1.07 s 

Ok:                  104
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-----------------------------

  parent reply	other threads:[~2024-06-14  0:04 UTC|newest]

Thread overview: 106+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240613225953.610732-1-joshwash@google.com>
2024-06-13 22:33 ` |SUCCESS| " qemudev
2024-06-13 22:38 ` qemudev
2024-06-13 23:01 ` |WARNING| " checkpatch
2024-06-13 23:46 ` |SUCCESS| pw141135 [PATCH] net/gve: change QPLs to be queue resource dpdklab
2024-06-13 23:52 ` dpdklab
2024-06-13 23:53 ` dpdklab
2024-06-13 23:53 ` dpdklab
2024-06-13 23:53 ` dpdklab
2024-06-13 23:54 ` dpdklab
2024-06-13 23:54 ` dpdklab
2024-06-13 23:54 ` dpdklab
2024-06-13 23:54 ` dpdklab
2024-06-13 23:55 ` dpdklab
2024-06-13 23:55 ` dpdklab
2024-06-13 23:55 ` dpdklab
2024-06-13 23:56 ` dpdklab
2024-06-13 23:57 ` dpdklab
2024-06-13 23:57 ` dpdklab
2024-06-13 23:57 ` dpdklab
2024-06-13 23:57 ` dpdklab
2024-06-13 23:57 ` dpdklab
2024-06-14  0:04 ` 0-day Robot [this message]
2024-06-14  0:09 ` dpdklab
2024-06-14  0:17 ` dpdklab
2024-06-14  0:18 ` dpdklab
2024-06-14  0:18 ` dpdklab
2024-06-14  0:23 ` dpdklab
2024-06-14  0:24 ` dpdklab
2024-06-14  0:26 ` dpdklab
2024-06-14  0:28 ` dpdklab
2024-06-14  0:28 ` dpdklab
2024-06-14  0:29 ` dpdklab
2024-06-14  0:30 ` dpdklab
2024-06-14  0:31 ` dpdklab
2024-06-14  0:31 ` dpdklab
2024-06-14  0:32 ` dpdklab
2024-06-14  0:32 ` dpdklab
2024-06-14  0:33 ` dpdklab
2024-06-14  0:33 ` dpdklab
2024-06-14  0:34 ` dpdklab
2024-06-14  0:35 ` dpdklab
2024-06-14  0:36 ` dpdklab
2024-06-14  0:41 ` dpdklab
2024-06-14  0:41 ` dpdklab
2024-06-14  0:42 ` dpdklab
2024-06-14  0:42 ` dpdklab
2024-06-14  0:42 ` dpdklab
2024-06-14  0:43 ` dpdklab
2024-06-14  0:43 ` dpdklab
2024-06-14  0:44 ` dpdklab
2024-06-14  0:44 ` dpdklab
2024-06-14  0:45 ` dpdklab
2024-06-14  0:45 ` dpdklab
2024-06-14  0:45 ` dpdklab
2024-06-14  0:45 ` dpdklab
2024-06-14  0:47 ` dpdklab
2024-06-14  0:47 ` dpdklab
2024-06-14  0:48 ` dpdklab
2024-06-14  0:50 ` dpdklab
2024-06-14  0:51 ` dpdklab
2024-06-14  0:52 ` dpdklab
2024-06-14  0:52 ` dpdklab
2024-06-14  0:53 ` dpdklab
2024-06-14  0:53 ` dpdklab
2024-06-14  0:53 ` dpdklab
2024-06-14  0:54 ` dpdklab
2024-06-14  0:54 ` dpdklab
2024-06-14  0:54 ` dpdklab
2024-06-14  0:54 ` dpdklab
2024-06-14  0:55 ` dpdklab
2024-06-14  0:55 ` dpdklab
2024-06-14  0:55 ` dpdklab
2024-06-14  0:55 ` dpdklab
2024-06-14  1:05 ` dpdklab
2024-06-14  1:05 ` dpdklab
2024-06-14  1:06 ` dpdklab
2024-06-14  1:07 ` dpdklab
2024-06-14  1:08 ` dpdklab
2024-06-14  1:09 ` dpdklab
2024-06-14  1:10 ` dpdklab
2024-06-14  1:10 ` dpdklab
2024-06-14  1:11 ` dpdklab
2024-06-14  1:11 ` dpdklab
2024-06-14  1:12 ` dpdklab
2024-06-14  1:12 ` dpdklab
2024-06-14  1:13 ` dpdklab
2024-06-14  1:14 ` dpdklab
2024-06-14  1:26 ` dpdklab
2024-06-14  1:28 ` dpdklab
2024-06-14  1:33 ` dpdklab
2024-06-14  1:34 ` dpdklab
2024-06-14  1:35 ` dpdklab
2024-06-14  1:37 ` dpdklab
2024-06-14  1:48 ` dpdklab
2024-06-14  1:50 ` dpdklab
2024-06-14  1:55 ` dpdklab
2024-06-14  1:56 ` dpdklab
2024-06-14  2:11 ` dpdklab
2024-06-14  2:12 ` dpdklab
2024-06-14  2:12 ` dpdklab
2024-06-14  2:18 ` dpdklab
2024-06-14  2:18 ` dpdklab
2024-06-14  2:19 ` dpdklab
2024-06-14  2:21 ` dpdklab
2024-06-14  2:23 ` dpdklab
2024-06-14  2:24 ` 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=20240614000439.3926472-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=joshwash@google.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).