automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: roretzla@linux.microsoft.com, robot@bytheb.org
Subject: |FAILURE| pw139515 [PATCH v2 19/19] build: enable vla warnings on Windows built code
Date: Thu, 18 Apr 2024 17:04:48 -0400	[thread overview]
Message-ID: <20240418210448.509756-1-robot@bytheb.org> (raw)
In-Reply-To: <1713470562-17415-20-git-send-email-roretzla@linux.microsoft.com>

From: robot@bytheb.org

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

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

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
88/97 DPDK:fast-tests / telemetry_json_autotest  OK       0.37 s 
89/97 DPDK:fast-tests / thash_autotest        OK       0.37 s 
90/97 DPDK:fast-tests / threads_autotest      OK       0.47 s 
91/97 DPDK:fast-tests / ticketlock_autotest   OK       0.42 s 
92/97 DPDK:fast-tests / timer_autotest        OK       2.87 s 
93/97 DPDK:fast-tests / trace_autotest        OK       0.37 s 
94/97 DPDK:fast-tests / trace_autotest_with_traces  OK       0.37 s 
95/97 DPDK:fast-tests / vdev_autotest         OK       0.37 s 
96/97 DPDK:fast-tests / version_autotest      OK       0.37 s 
97/97 DPDK:fast-tests / telemetry_all         OK       1.12 s 

Ok:                   90
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-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-04-18 21:04 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1713470562-17415-20-git-send-email-roretzla@linux.microsoft.com>
2024-04-18 19:43 ` |SUCCESS| pw139497-139515 " qemudev
2024-04-18 19:47 ` qemudev
2024-04-18 20:05 ` |SUCCESS| pw139515 " checkpatch
2024-04-18 21:02 ` |SUCCESS| pw139497-139515 [PATCH] [v2,19/19] build: enable vla warni dpdklab
2024-04-18 21:04 ` 0-day Robot [this message]
2024-04-18 21:13 ` dpdklab
2024-04-18 21:13 ` dpdklab
2024-04-18 21:14 ` dpdklab
2024-04-18 21:14 ` dpdklab
2024-04-18 21:15 ` dpdklab
2024-04-18 21:15 ` dpdklab
2024-04-18 21:15 ` dpdklab
2024-04-18 21:16 ` dpdklab
2024-04-18 21:16 ` dpdklab
2024-04-18 21:16 ` dpdklab
2024-04-18 21:16 ` dpdklab
2024-04-18 21:17 ` dpdklab
2024-04-18 21:17 ` dpdklab
2024-04-18 21:17 ` dpdklab
2024-04-18 21:17 ` dpdklab
2024-04-18 21:18 ` dpdklab
2024-04-18 21:18 ` dpdklab
2024-04-18 21:19 ` dpdklab
2024-04-18 21:19 ` dpdklab
2024-04-18 21:20 ` dpdklab
2024-04-18 21:26 ` dpdklab
2024-04-18 21:26 ` dpdklab
2024-04-18 21:26 ` dpdklab
2024-04-18 21:27 ` dpdklab
2024-04-18 21:27 ` dpdklab
2024-04-18 21:28 ` dpdklab
2024-04-18 21:28 ` dpdklab
2024-04-18 21:29 ` dpdklab
2024-04-18 21:29 ` dpdklab
2024-04-18 21:30 ` dpdklab
2024-04-18 21:31 ` dpdklab
2024-04-18 21:31 ` dpdklab
2024-04-18 21:31 ` dpdklab
2024-04-18 21:32 ` dpdklab
2024-04-18 21:32 ` dpdklab
2024-04-18 21:32 ` dpdklab
2024-04-18 21:32 ` dpdklab
2024-04-18 21:33 ` dpdklab
2024-04-18 21:33 ` dpdklab
2024-04-18 21:33 ` dpdklab
2024-04-18 21:34 ` dpdklab
2024-04-18 21:36 ` dpdklab
2024-04-18 21:37 ` dpdklab
2024-04-18 21:37 ` dpdklab
2024-04-18 21:37 ` dpdklab
2024-04-18 21:38 ` dpdklab
2024-04-18 21:39 ` dpdklab
2024-04-18 21:40 ` dpdklab
2024-04-18 21:40 ` dpdklab
2024-04-18 21:41 ` dpdklab
2024-04-18 21:41 ` dpdklab
2024-04-18 21:41 ` dpdklab
2024-04-18 21:42 ` dpdklab
2024-04-18 21:42 ` dpdklab
2024-04-18 21:42 ` dpdklab
2024-04-18 21:42 ` dpdklab
2024-04-18 21:42 ` dpdklab
2024-04-18 21:43 ` dpdklab
2024-04-18 21:43 ` dpdklab
2024-04-18 21:43 ` dpdklab
2024-04-18 21:52 ` dpdklab
2024-04-18 21:53 ` dpdklab
2024-04-18 22:14 ` dpdklab
2024-04-18 22:14 ` dpdklab
2024-04-18 22:15 ` dpdklab
2024-04-18 22:15 ` dpdklab
2024-04-18 22:15 ` dpdklab
2024-04-18 22:15 ` dpdklab
2024-04-18 22:16 ` dpdklab
2024-04-18 22:16 ` dpdklab
2024-04-18 22:17 ` dpdklab
2024-04-18 22:17 ` dpdklab
2024-04-18 22:17 ` dpdklab
2024-04-18 22:18 ` dpdklab
2024-04-18 22:19 ` dpdklab
2024-04-18 22:19 ` dpdklab
2024-04-18 22:20 ` dpdklab
2024-04-18 22:20 ` dpdklab
2024-04-18 22:20 ` dpdklab
2024-04-18 22:21 ` dpdklab
2024-04-18 22:23 ` dpdklab
2024-04-18 22:23 ` dpdklab
2024-04-18 22:25 ` dpdklab
2024-04-18 22:41 ` dpdklab
2024-04-18 23:04 ` dpdklab
2024-04-18 23:41 ` dpdklab
2024-04-19  0:37 ` 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=20240418210448.509756-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=roretzla@linux.microsoft.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).