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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 340c178977a29d2bffa4e43122207ce3a02be7ee
Date: Sat, 21 Dec 2024 23:02:56 -0800 (PST)	[thread overview]
Message-ID: <6767b9a0.050a0220.246f5b.ca5dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v21.11

340c178977a29d2bffa4e43122207ce3a02be7ee --> testing issues

Upstream job id: Generic-Unit-Test-DPDK#301136

Test environment and result as below:

+-------------------+----------------+
|    Environment    | dpdk_unit_test |
+===================+================+
| Fedora 39 (Clang) | FAIL           |
+-------------------+----------------+
| RHEL8             | FAIL           |
+-------------------+----------------+
| Debian Bullseye   | FAIL           |
+-------------------+----------------+
| Fedora 40 (Clang) | FAIL           |
+-------------------+----------------+
| Debian 12         | FAIL           |
+-------------------+----------------+
| CentOS Stream 9   | FAIL           |
+-------------------+----------------+
| RHEL9             | FAIL           |
+-------------------+----------------+
| Fedora 39         | FAIL           |
+-------------------+----------------+
| Ubuntu 22.04      | FAIL           |
+-------------------+----------------+
| Ubuntu 20.04      | FAIL           |
+-------------------+----------------+
| Fedora 40         | FAIL           |
+-------------------+----------------+
| Ubuntu 24.04      | FAIL           |
+-------------------+----------------+

==== Unit test summary for Ubuntu 24.04 (dpdk_unit_test): ====
ninja: Entering directory `/home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build'
ninja: no work to do.
  1/101 DPDK:fast-tests / acl_autotest          OK       5.42 s 
  2/101 DPDK:fast-tests / atomic_autotest       OK       1.02 s 
  3/101 DPDK:fast-tests / bitmap_autotest       OK       0.30 s 
  4/101 DPDK:fast-tests / bpf_autotest          OK       0.23 s 
  5/101 DPDK:fast-tests / bpf_convert_autotest  OK       0.25 s 
  6/101 DPDK:fast-tests / bitops_autotest       OK       0.38 s 
  7/101 DPDK:fast-tests / byteorder_autotest    OK       0.21 s 
  8/101 DPDK:fast-tests / cksum_autotest        OK       0.30 s 
  9/101 DPDK:fast-tests / cmdline_autotest      OK       0.40 s 
 10/101 DPDK:fast-tests / common_autotest       OK       1.06 s 
 11/101 DPDK:fast-tests / cpuflags_autotest     OK       0.35 s 
 12/101 DPDK:fast-tests / debug_autotest        OK       0.81 s 
 13/101 DPDK:fast-tests / devargs_autotest      OK       0.24 s 
 14/101 DPDK:fast-tests / eal_flags_c_opt_autotest  OK       1.50 s 
 15/101 DPDK:fast-tests / eal_flags_main_opt_autotest  OK       0.51 s 
 16/101 DPDK:fast-tests / eal_flags_n_opt_autotest  OK       0.69 s 
 17/101 DPDK:fast-tests / eal_flags_hpet_autotest  OK       0.41 s 
 18/101 DPDK:fast-tests / eal_flags_no_huge_autotest  OK       0.70 s 
 19/101 DPDK:fast-tests / eal_flags_a_opt_autotest  OK       0.46 s 
 20/101 DPDK:fast-tests / eal_flags_b_opt_autotest  OK       0.64 s 
 21/101 DPDK:fast-tests / eal_flags_vdev_opt_autotest  OK       0.79 s 
 22/101 DPDK:fast-tests / eal_flags_r_opt_autotest  OK       0.42 s 
 23/101 DPDK:fast-tests / eal_flags_mem_autotest  OK       1.11 s 
 24/101 DPDK:fast-tests / eal_flags_file_prefix_autotest  OK       5.28 s 
 25/101 DPDK:fast-tests / eal_flags_misc_autotest  OK       2.58 s 
 26/101 DPDK:fast-tests / eal_fs_autotest       OK       0.25 s 
 27/101 DPDK:fast-tests / errno_autotest        OK       0.17 s 
 28/101 DPDK:fast-tests / ethdev_link_status    OK       0.20 s 
 29/101 DPDK:fast-tests / event_ring_autotest   OK       0.17 s 
 30/101 DPDK:fast-tests / fib_autotest          OK       1.17 s 
 31/101 DPDK:fast-tests / fib6_autotest         OK       0.95 s 
 32/101 DPDK:fast-tests / func_reentrancy_autotest  OK       0.93 s 
 33/101 DPDK:fast-tests / flow_classify_autotest  OK       0.16 s 
 34/101 DPDK:fast-tests / graph_autotest        OK       0.23 s 
 35/101 DPDK:fast-tests / hash_autotest         OK       0.38 s 
 36/101 DPDK:fast-tests / interrupt_autotest    OK       1.65 s 
 37/101 DPDK:fast-tests / ipfrag_autotest       OK       0.24 s 
 38/101 DPDK:fast-tests / lcores_autotest       OK       2.86 s 
 39/101 DPDK:fast-tests / logs_autotest         OK       0.22 s 
 40/101 DPDK:fast-tests / lpm_autotest          OK       6.73 s 
 41/101 DPDK:fast-tests / lpm6_autotest         OK       8.38 s 
 42/101 DPDK:fast-tests / malloc_autotest       OK       1.07 s 
 43/101 DPDK:fast-tests / mbuf_autotest         OK       0.44 s 
 44/101 DPDK:fast-tests / mcslock_autotest      OK       0.70 s 
 45/101 DPDK:fast-tests / memcpy_autotest       OK       2.97 s 
 46/101 DPDK:fast-tests / memory_autotest       OK       0.19 s 
 47/101 DPDK:fast-tests / mempool_autotest      OK       0.50 s 
 48/101 DPDK:fast-tests / memzone_autotest      OK       0.20 s 
 49/101 DPDK:fast-tests / meter_autotest        OK       0.16 s 
 50/101 DPDK:fast-tests / multiprocess_autotest  OK       0.46 s 
 51/101 DPDK:fast-tests / node_list_dump        OK       0.22 s 
 52/101 DPDK:fast-tests / per_lcore_autotest    OK       0.36 s 
 53/101 DPDK:fast-tests / pflock_autotest       OK       0.36 s 
 54/101 DPDK:fast-tests / prefetch_autotest     OK       0.20 s 
 55/101 DPDK:fast-tests / rcu_qsbr_autotest     OK       0.41 s 
 56/101 DPDK:fast-tests / pie_autotest          OK       0.17 s 
 57/101 DPDK:fast-tests / rib_autotest          OK       7.13 s 
 58/101 DPDK:fast-tests / rib6_autotest         OK       8.40 s 
 59/101 DPDK:fast-tests / ring_autotest         OK       0.21 s 
 60/101 DPDK:fast-tests / rwlock_test1_autotest  OK       0.26 s 
 61/101 DPDK:fast-tests / rwlock_rda_autotest   OK       5.21 s 
 62/101 DPDK:fast-tests / rwlock_rds_wrm_autotest  OK       5.28 s 
 63/101 DPDK:fast-tests / rwlock_rde_wro_autotest  OK       5.23 s 
 64/101 DPDK:fast-tests / sched_autotest        OK       0.23 s 
 65/101 DPDK:fast-tests / security_autotest     OK       0.23 s 
 66/101 DPDK:fast-tests / spinlock_autotest     OK       0.18 s 
 67/101 DPDK:fast-tests / stack_autotest        OK       0.34 s 
 68/101 DPDK:fast-tests / stack_lf_autotest     OK       0.24 s 
 69/101 DPDK:fast-tests / string_autotest       OK       0.21 s 
 70/101 DPDK:fast-tests / table_autotest        FAIL     1.62 s (exit status 255 or signal 127 SIGinvalid)
 71/101 DPDK:fast-tests / tailq_autotest        OK       0.24 s 
 72/101 DPDK:fast-tests / ticketlock_autotest   OK       0.26 s 
 73/101 DPDK:fast-tests / timer_autotest        OK       2.71 s 
 74/101 DPDK:fast-tests / user_delay_us         OK       0.24 s 
 75/101 DPDK:fast-tests / version_autotest      OK       0.29 s 
 76/101 DPDK:fast-tests / crc_autotest          OK       0.28 s 
 77/101 DPDK:fast-tests / distributor_autotest  OK       2.30 s 
 78/101 DPDK:fast-tests / eventdev_common_autotest  OK       0.36 s 
 79/101 DPDK:fast-tests / fbarray_autotest      OK       0.15 s 
 80/101 DPDK:fast-tests / hash_readwrite_func_autotest  SKIP     0.32 s 
 81/101 DPDK:fast-tests / ipsec_autotest        SKIP     0.24 s 
 82/101 DPDK:fast-tests / kni_autotest          SKIP     0.26 s 
 83/101 DPDK:fast-tests / kvargs_autotest       OK       0.30 s 
 84/101 DPDK:fast-tests / member_autotest       OK       0.25 s 
 85/101 DPDK:fast-tests / power_cpufreq_autotest  SKIP     0.36 s 
 86/101 DPDK:fast-tests / power_autotest        OK       0.20 s 
 87/101 DPDK:fast-tests / power_kvm_vm_autotest  SKIP     0.18 s 
 88/101 DPDK:fast-tests / reorder_autotest      OK       0.27 s 
 89/101 DPDK:fast-tests / service_autotest      OK       1.49 s 
 90/101 DPDK:fast-tests / thash_autotest        OK       0.22 s 
 91/101 DPDK:fast-tests / trace_autotest        OK       0.17 s 
 92/101 DPDK:fast-tests / metrics_autotest      OK       0.28 s 
 93/101 DPDK:fast-tests / telemetry_json_autotest  OK       0.16 s 
 94/101 DPDK:fast-tests / telemetry_data_autotest  OK       0.15 s 
 95/101 DPDK:fast-tests / ring_pmd_autotest     OK       0.25 s 
 96/101 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK       0.74 s 
 97/101 DPDK:fast-tests / bitratestats_autotest  OK       0.17 s 
 98/101 DPDK:fast-tests / latencystats_autotest  OK       0.15 s 
 99/101 DPDK:fast-tests / pdump_autotest        OK       5.31 s 
100/101 DPDK:fast-tests / vdev_autotest         OK       0.17 s 
101/101 DPDK:fast-tests / compressdev_autotest  SKIP     0.17 s 

Ok:                   94
Expected Fail:         0
Fail:                  1
Unexpected Pass:       0
Skipped:               6
Timeout:               0

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



Test log output from the failed test table_autotest:

Sorry, we were not able to find the logs for this test.
Download the log output from the CI site for this test run.
==== End log output ====

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/32013/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-22  7:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-22  7:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-22  7:39 dpdklab
2024-12-22  7:38 dpdklab
2024-12-21  8:17 dpdklab
2024-12-21  8:11 dpdklab
2024-12-21  8:08 dpdklab
2024-12-21  8:03 dpdklab
2024-12-21  8:00 dpdklab
2024-12-21  7:58 dpdklab
2024-12-21  7:57 dpdklab
2024-12-21  7:56 dpdklab
2024-12-21  7:55 dpdklab
2024-12-21  7:55 dpdklab
2024-12-21  7:48 dpdklab
2024-12-21  7:19 dpdklab
2024-12-20  8:32 dpdklab
2024-12-20  8:00 dpdklab
2024-12-20  7:23 dpdklab
2024-12-20  7:23 dpdklab
2024-12-20  7:11 dpdklab
2024-12-19  7:42 dpdklab
2024-12-19  7:26 dpdklab
2024-12-19  6:41 dpdklab
2024-12-19  6:09 dpdklab
2024-12-19  6:02 dpdklab
2024-12-19  5:46 dpdklab
2024-12-19  5:33 dpdklab
2024-12-18 10:06 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=6767b9a0.050a0220.246f5b.ca5dSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).