automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |FAILURE| pw138955-138956 [PATCH] [v2,4/4] net/virtio-user: fix cont
Date: Thu, 28 Mar 2024 09:43:39 -0700 (PDT)	[thread overview]
Message-ID: <66059e3b.170a0220.bf8be.3e79SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240328130813.3696005-5-maxime.coquelin@redhat.com>

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138956

_Testing issues_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Thursday, March 28 2024 13:08:13 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d

138955-138956 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Debian 11 (arm)     | FAIL           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+

==== 20 line log output for Debian 11 (arm) (dpdk_unit_test): ====
102/112 DPDK:fast-tests / telemetry_data_autotest        OK               0.18s
103/112 DPDK:fast-tests / telemetry_json_autotest        OK               0.17s
104/112 DPDK:fast-tests / thash_autotest                 OK               0.18s
105/112 DPDK:fast-tests / threads_autotest               OK               0.34s
106/112 DPDK:fast-tests / ticketlock_autotest            OK               0.19s
107/112 DPDK:fast-tests / timer_autotest                 OK               2.49s
108/112 DPDK:fast-tests / trace_autotest                 OK               0.18s
109/112 DPDK:fast-tests / trace_autotest_with_traces     OK               0.18s
110/112 DPDK:fast-tests / vdev_autotest                  OK               0.17s
111/112 DPDK:fast-tests / version_autotest               OK               0.17s
112/112 DPDK:fast-tests / telemetry_all                  SKIP             0.01s   exit status 77

Ok:                 101
Expected Fail:      0
Fail:               1
Unexpected Pass:    0
Skipped:            10
Timeout:            0

Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
==== End log output ====

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29674/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-03-28 16:43 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240328130813.3696005-5-maxime.coquelin@redhat.com>
2024-03-28 12:45 ` |SUCCESS| pw138955-138956 [PATCH v2 4/4] net/virtio-user: fix control queue allocation qemudev
2024-03-28 12:50 ` qemudev
2024-03-28 13:10 ` |SUCCESS| pw138956 " checkpatch
2024-03-28 14:05 ` 0-day Robot
2024-03-28 14:48 ` |SUCCESS| pw138955-138956 [PATCH] [v2,4/4] net/virtio-user: fix cont dpdklab
2024-03-28 14:50 ` dpdklab
2024-03-28 14:50 ` dpdklab
2024-03-28 14:50 ` dpdklab
2024-03-28 14:51 ` dpdklab
2024-03-28 14:51 ` dpdklab
2024-03-28 14:52 ` dpdklab
2024-03-28 14:52 ` dpdklab
2024-03-28 14:53 ` dpdklab
2024-03-28 14:54 ` dpdklab
2024-03-28 14:55 ` dpdklab
2024-03-28 14:55 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:57 ` dpdklab
2024-03-28 15:02 ` dpdklab
2024-03-28 15:09 ` dpdklab
2024-03-28 15:15 ` dpdklab
2024-03-28 15:42 ` dpdklab
2024-03-28 15:46 ` dpdklab
2024-03-28 15:56 ` dpdklab
2024-03-28 16:01 ` dpdklab
2024-03-28 16:02 ` dpdklab
2024-03-28 16:05 ` dpdklab
2024-03-28 16:05 ` dpdklab
2024-03-28 16:07 ` dpdklab
2024-03-28 16:09 ` dpdklab
2024-03-28 16:10 ` dpdklab
2024-03-28 16:10 ` dpdklab
2024-03-28 16:11 ` dpdklab
2024-03-28 16:11 ` dpdklab
2024-03-28 16:13 ` dpdklab
2024-03-28 16:13 ` dpdklab
2024-03-28 16:14 ` dpdklab
2024-03-28 16:15 ` dpdklab
2024-03-28 16:15 ` dpdklab
2024-03-28 16:16 ` dpdklab
2024-03-28 16:16 ` dpdklab
2024-03-28 16:18 ` dpdklab
2024-03-28 16:19 ` dpdklab
2024-03-28 16:19 ` dpdklab
2024-03-28 16:20 ` dpdklab
2024-03-28 16:22 ` dpdklab
2024-03-28 16:23 ` dpdklab
2024-03-28 16:24 ` dpdklab
2024-03-28 16:25 ` dpdklab
2024-03-28 16:27 ` dpdklab
2024-03-28 16:27 ` dpdklab
2024-03-28 16:28 ` dpdklab
2024-03-28 16:28 ` |FAILURE| " dpdklab
2024-03-28 16:30 ` |SUCCESS| " dpdklab
2024-03-28 16:31 ` dpdklab
2024-03-28 16:32 ` dpdklab
2024-03-28 16:32 ` dpdklab
2024-03-28 16:39 ` |FAILURE| " dpdklab
2024-03-28 16:39 ` |SUCCESS| " dpdklab
2024-03-28 16:39 ` dpdklab
2024-03-28 16:40 ` dpdklab
2024-03-28 16:41 ` dpdklab
2024-03-28 16:43 ` dpdklab
2024-03-28 16:43 ` dpdklab
2024-03-28 16:43 ` dpdklab [this message]
2024-03-28 16:45 ` dpdklab
2024-03-28 16:45 ` |FAILURE| " dpdklab
2024-03-28 16:45 ` |SUCCESS| " dpdklab
2024-03-28 16:46 ` dpdklab
2024-03-28 16:50 ` dpdklab
2024-03-28 16:58 ` dpdklab
2024-03-28 16:58 ` dpdklab
2024-03-28 16:59 ` |FAILURE| " dpdklab
2024-03-28 16:59 ` |SUCCESS| " dpdklab
2024-03-28 17:00 ` dpdklab
2024-03-28 17:00 ` |FAILURE| " dpdklab
2024-03-28 17:01 ` |SUCCESS| " dpdklab
2024-03-28 17:02 ` dpdklab
2024-03-28 17:06 ` dpdklab
2024-03-28 17:07 ` dpdklab
2024-03-28 17:07 ` dpdklab
2024-03-28 17:16 ` dpdklab
2024-03-28 17:27 ` dpdklab
2024-03-28 17:33 ` dpdklab
2024-03-28 18:09 ` dpdklab
2024-03-28 18:10 ` dpdklab
2024-04-02 16:47 ` dpdklab
2024-04-02 16:52 ` dpdklab
2024-04-02 16:55 ` dpdklab
2024-04-02 17:02 ` dpdklab
2024-04-02 17:25 ` 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=66059e3b.170a0220.bf8be.3e79SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=maxime.coquelin@redhat.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).