automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: liwg06@foxmail.com, robot@bytheb.org
Subject: |FAILURE| pw108368 [PATCH] sched: add parentheses to if clause
Date: Sat, 26 Feb 2022 11:58:31 -0500	[thread overview]
Message-ID: <20220226165831.9055-1-robot@bytheb.org> (raw)
In-Reply-To: <tencent_353E2247E7FA1B6FA44C8421A689C7ED7405@qq.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/108368/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1903441610
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-18.04-gcc-shared-abi+doc+tests" failed at step Build and test
"ubuntu-18.04-clang-shared-doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-18.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################
90/99 DPDK:fast-tests / telemetry_json_autotest  OK       0.17 s 
91/99 DPDK:fast-tests / telemetry_data_autotest  OK       0.17 s 
92/99 DPDK:fast-tests / table_autotest        OK       8.14 s 
93/99 DPDK:fast-tests / ring_pmd_autotest     OK       0.17 s 
94/99 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK       0.67 s 
95/99 DPDK:fast-tests / bitratestats_autotest  OK       0.17 s 
96/99 DPDK:fast-tests / latencystats_autotest  OK       0.17 s 
97/99 DPDK:fast-tests / pdump_autotest        OK       5.23 s 
98/99 DPDK:fast-tests / vdev_autotest         OK       0.17 s 
99/99 DPDK:fast-tests / compressdev_autotest  SKIP     0.17 s 

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

Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-18.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-18.04-clang-shared-doc+tests" at step Build and test
####################################################################################
90/99 DPDK:fast-tests / telemetry_json_autotest  OK       0.17 s 
91/99 DPDK:fast-tests / telemetry_data_autotest  OK       0.17 s 
92/99 DPDK:fast-tests / table_autotest        OK       7.09 s 
93/99 DPDK:fast-tests / ring_pmd_autotest     OK       0.17 s 
94/99 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK       0.67 s 
95/99 DPDK:fast-tests / bitratestats_autotest  OK       0.17 s 
96/99 DPDK:fast-tests / latencystats_autotest  OK       0.17 s 
97/99 DPDK:fast-tests / pdump_autotest        OK       5.23 s 
98/99 DPDK:fast-tests / vdev_autotest         OK       0.17 s 
99/99 DPDK:fast-tests / compressdev_autotest  SKIP     0.17 s 

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

Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-18.04-clang-shared-doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2022-02-26 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_353E2247E7FA1B6FA44C8421A689C7ED7405@qq.com>
2022-02-26 14:55 ` |SUCCESS| " checkpatch
2022-02-26 16:58 ` 0-day Robot [this message]
2022-02-27  2:04 |FAILURE| " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2022-02-26 15:58 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=20220226165831.9055-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=liwg06@foxmail.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).