DPDK CI discussions
 help / color / mirror / Atom feed
From: William Tu <u9012063@gmail.com>
To: ci@dpdk.org
Subject: [dpdk-ci] Fwd: |FAILURE| pw97283 [PATCH] [v9] eal: remove sys/queue.h from public headers
Date: Wed, 1 Sep 2021 09:34:36 -0700	[thread overview]
Message-ID: <CALDO+SZ5vvx+dmx5L=1LfHeCYU8-b07OcYNG57tDyVbqBW8n+w@mail.gmail.com> (raw)
In-Reply-To: <20210825184223.50742B0FE@noxus.dpdklab.iol.unh.edu>

Hi,
Can you trigger the test again?
I think this fails due to the test framework issue, not the patch.
Thanks
William

---------- Forwarded message ---------
From: <dpdklab@iol.unh.edu>
Date: Wed, Aug 25, 2021 at 11:42 AM
Subject: |FAILURE| pw97283 [PATCH] [v9] eal: remove sys/queue.h from
public headers
To: Test Report <test-report@dpdk.org>
Cc: <dpdk-test-reports@iol.unh.edu>, William Tu <u9012063@gmail.com>


Test-Label: iol-aarch64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/97283

_Testing issues_

Submitter: William Tu <u9012063@gmail.com>
Date: Tuesday, August 24 2021 16:21:03
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fdab8f2e17493192d555cd88cf28b06269174326

97283 --> testing fail

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| Ubuntu 20.04 ARM | FAIL           |
+------------------+----------------+

==== 20 line log output for Ubuntu 20.04 ARM (dpdk_unit_test): ====
85/94 DPDK:fast-tests / thash_autotest                 OK                0.32s
86/94 DPDK:fast-tests / trace_autotest                 OK                0.47s
87/94 DPDK:fast-tests / telemetry_json_autotest        OK                0.43s
88/94 DPDK:fast-tests / telemetry_data_autotest        OK                0.44s
89/94 DPDK:fast-tests / ring_pmd_autotest              OK                0.31s
90/94 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK                1.43s
91/94 DPDK:fast-tests / bitratestats_autotest          OK                0.33s
92/94 DPDK:fast-tests / latencystats_autotest          OK                0.36s
93/94 DPDK:fast-tests / pdump_autotest                 OK                5.43s
94/94 DPDK:fast-tests / compressdev_autotest           SKIP
  0.43s   exit status 77


Ok:                 89
Expected Fail:      0
Fail:               1
Unexpected Pass:    0
Skipped:            4
Timeout:            0

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

Ubuntu 20.04 ARM
        Kernel: 5.4.0-53-generic
        Compiler: gcc 9.3

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

UNH-IOL DPDK Community Lab

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

       reply	other threads:[~2021-09-01 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210825184223.50742B0FE@noxus.dpdklab.iol.unh.edu>
2021-09-01 16:34 ` William Tu [this message]
2021-09-02 13:51   ` Brandon Lo

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='CALDO+SZ5vvx+dmx5L=1LfHeCYU8-b07OcYNG57tDyVbqBW8n+w@mail.gmail.com' \
    --to=u9012063@gmail.com \
    --cc=ci@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).