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, Thomas Monjalon <thomas@monjalon.net>
Subject: |FAILURE| pw133312-133313 [PATCH] [v3,2/2] eal/unix: allow creating
Date: Wed, 25 Oct 2023 15:42:47 -0700 (PDT)	[thread overview]
Message-ID: <653999e7.d40a0220.a5cb6.622fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/133313

_Testing issues_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Wednesday, October 25 2023 16:31:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2a0557d1ea21c3f63a212385348c97c414970e81

133312-133313 --> testing fail

Test environment and result as below:

+--------------------------+----------------+--------------+
|       Environment        | dpdk_unit_test | lpm_autotest |
+==========================+================+==============+
| Debian 11 (Buster) (ARM) | PASS           | SKIPPED      |
+--------------------------+----------------+--------------+
| Fedora 37 (ARM)          | PASS           | SKIPPED      |
+--------------------------+----------------+--------------+
| CentOS Stream 9 (ARM)    | FAIL           | SKIPPED      |
+--------------------------+----------------+--------------+
| Fedora 38 (ARM)          | PASS           | SKIPPED      |
+--------------------------+----------------+--------------+
| Fedora 38 (ARM Clang)    | PASS           | SKIPPED      |
+--------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE     | SKIPPED        | PASS         |
+--------------------------+----------------+--------------+

==== 20 line log output for CentOS Stream 9 (ARM) (dpdk_unit_test): ====
100/110 DPDK:fast-tests / telemetry_data_autotest  OK       0.17 s
101/110 DPDK:fast-tests / telemetry_json_autotest  OK       0.17 s
102/110 DPDK:fast-tests / thash_autotest        OK       0.17 s
103/110 DPDK:fast-tests / threads_autotest      TIMEOUT 600.01 s
104/110 DPDK:fast-tests / ticketlock_autotest   OK       0.23 s
105/110 DPDK:fast-tests / timer_autotest        OK       2.83 s
106/110 DPDK:fast-tests / trace_autotest        OK       0.17 s
107/110 DPDK:fast-tests / trace_autotest_with_traces  OK       0.17 s
108/110 DPDK:fast-tests / vdev_autotest         OK       0.17 s
109/110 DPDK:fast-tests / version_autotest      OK       0.17 s
110/110 DPDK:fast-tests / telemetry_all         SKIP     0.01 s

Ok:                  102
Expected Fail:         0
Fail:                  0
Unexpected Pass:       0
Skipped:               7
Timeout:               1

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

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-25 22:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 22:42 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-25 23:13 dpdklab
2023-10-25 23:00 dpdklab
2023-10-25 22:44 dpdklab
2023-10-25 22:39 dpdklab
2023-10-25 22:20 dpdklab
2023-10-25 22:16 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=653999e7.d40a0220.a5cb6.622fSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).