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,
	Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Subject: |FAILURE| pw136876-136877 [PATCH] [RFC,v2,5/5] service: keep per-lco
Date: Mon, 19 Feb 2024 03:07:11 -0800 (PST)	[thread overview]
Message-ID: <65d3365f.810a0220.ee194.7c72SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Monday, February 19 2024 09:40:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3cb34fb0b0adfeb163b4d0e6d5a232a21bd6f6e0

136876-136877 --> testing fail

Test environment and result as below:

+-----------------------+--------------+----------------+
|      Environment      | lpm_autotest | dpdk_unit_test |
+=======================+==============+================+
| Ubuntu 20.04 ARM SVE  | PASS         | SKIPPED        |
+-----------------------+--------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED      | FAIL           |
+-----------------------+--------------+----------------+

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

Ok:                  104
Expected Fail:         0
Fail:                  1
Unexpected Pass:       0
Skipped:               7
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 ====

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-19 11:07 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 11:07 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-19 11:32 dpdklab
2024-02-19 11:29 dpdklab
2024-02-19 11:27 dpdklab
2024-02-19 11:24 dpdklab
2024-02-19 11:23 dpdklab
2024-02-19 11:20 dpdklab
2024-02-19 11:17 dpdklab
2024-02-19 11:16 dpdklab
2024-02-19 11:15 dpdklab
2024-02-19 11:14 dpdklab
2024-02-19 11:08 dpdklab
2024-02-19 11:07 dpdklab
2024-02-19 11:06 dpdklab
2024-02-19 11:04 dpdklab
2024-02-19 11:04 dpdklab
2024-02-19 10:57 dpdklab
2024-02-19 10:55 dpdklab
2024-02-19 10:55 dpdklab
2024-02-19 10:54 dpdklab
2024-02-19 10:54 dpdklab
2024-02-19 10:54 dpdklab
2024-02-19 10:54 dpdklab
2024-02-19 10:53 dpdklab
2024-02-19 10:53 dpdklab
2024-02-19 10:52 dpdklab
2024-02-19 10:52 dpdklab
2024-02-19 10:50 dpdklab
2024-02-19 10:48 dpdklab
2024-02-19 10:48 dpdklab
2024-02-19 10:46 dpdklab
2024-02-19 10:35 dpdklab
2024-02-19 10:34 dpdklab
2024-02-19 10:34 dpdklab
2024-02-19 10:30 dpdklab
2024-02-19 10:29 dpdklab
2024-02-19 10:29 dpdklab
2024-02-19 10:29 dpdklab
2024-02-19 10:28 dpdklab
2024-02-19 10:28 dpdklab
2024-02-19 10:27 dpdklab
2024-02-19 10:26 dpdklab
2024-02-19 10: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=65d3365f.810a0220.ee194.7c72SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=mattias.ronnblom@ericsson.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).