automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: xuemingl@nvidia.com, robot@bytheb.org
Subject: |FAILURE| pw108308 [PATCH v2 7/7] vdpa/mlx5: make statistics counter persistent
Date: Thu, 24 Feb 2022 12:38:37 -0500	[thread overview]
Message-ID: <20220224173837.32031-1-robot@bytheb.org> (raw)
In-Reply-To: <20220224155101.1991626-8-xuemingl@nvidia.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1894027088
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-18.04-clang-static" 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-clang-static" at step Build and test
####################################################################################
                                        (int)virtq->index);
                                        ^~~~~~~~~~~~~~~~~
../drivers/vdpa/mlx5/mlx5_vdpa_utils.h:17:3: note: expanded from macro 'DRV_LOG'
                __VA_ARGS__ PMD_DRV_LOG_STRIP PMD_DRV_LOG_OPAREN, \
                ^~~~~~~~~~~
../drivers/common/mlx5/mlx5_common.h:91:43: note: expanded from macro 'PMD_DRV_LOG_'
        PMD_DRV_LOG__(level, type, name, s "\n", __VA_ARGS__)
                                         ~       ^~~~~~~~~~~
../drivers/common/mlx5/mlx5_common.h:89:36: note: expanded from macro 'PMD_DRV_LOG__'
        PMD_DRV_LOG___(level, type, name, __VA_ARGS__)
                                          ^~~~~~~~~~~
../drivers/common/mlx5/mlx5_common.h:73:16: note: expanded from macro 'PMD_DRV_LOG___'
                RTE_FMT_TAIL(__VA_ARGS__,)))
                             ^~~~~~~~~~~
../lib/eal/include/rte_common.h:812:32: note: expanded from macro 'RTE_FMT_TAIL'
#define RTE_FMT_TAIL(fmt, ...) __VA_ARGS__
                               ^~~~~~~~~~~
../lib/eal/include/rte_common.h:810:39: note: expanded from macro 'RTE_FMT'
#define RTE_FMT(fmt, ...) fmt "%.0s", __VA_ARGS__ ""
                          ~~~         ^~~~~~~~~~~
1 error generated.
[2584/4417] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_mlx5@sta/vdpa_mlx5_mlx5_vdpa_lm.c.o'.
[2585/4417] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_mlx5@sta/vdpa_mlx5_mlx5_vdpa_event.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-18.04-clang-static" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-18.04-clang-shared-doc+tests" at step Build and test
####################################################################################
                                        (int)virtq->index);
                                        ^~~~~~~~~~~~~~~~~
../drivers/vdpa/mlx5/mlx5_vdpa_utils.h:17:3: note: expanded from macro 'DRV_LOG'
                __VA_ARGS__ PMD_DRV_LOG_STRIP PMD_DRV_LOG_OPAREN, \
                ^~~~~~~~~~~
../drivers/common/mlx5/mlx5_common.h:91:43: note: expanded from macro 'PMD_DRV_LOG_'
        PMD_DRV_LOG__(level, type, name, s "\n", __VA_ARGS__)
                                         ~       ^~~~~~~~~~~
../drivers/common/mlx5/mlx5_common.h:89:36: note: expanded from macro 'PMD_DRV_LOG__'
        PMD_DRV_LOG___(level, type, name, __VA_ARGS__)
                                          ^~~~~~~~~~~
../drivers/common/mlx5/mlx5_common.h:73:16: note: expanded from macro 'PMD_DRV_LOG___'
                RTE_FMT_TAIL(__VA_ARGS__,)))
                             ^~~~~~~~~~~
../lib/eal/include/rte_common.h:812:32: note: expanded from macro 'RTE_FMT_TAIL'
#define RTE_FMT_TAIL(fmt, ...) __VA_ARGS__
                               ^~~~~~~~~~~
../lib/eal/include/rte_common.h:810:39: note: expanded from macro 'RTE_FMT'
#define RTE_FMT(fmt, ...) fmt "%.0s", __VA_ARGS__ ""
                          ~~~         ^~~~~~~~~~~
1 error generated.
[2560/4597] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_mlx5@sta/vdpa_mlx5_mlx5_vdpa_lm.c.o'.
[2561/4597] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_mlx5@sta/vdpa_mlx5_mlx5_vdpa_event.c.o'.
ninja: build stopped: subcommand failed.
##[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-24 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220224155101.1991626-8-xuemingl@nvidia.com>
2022-02-24 15:54 ` |SUCCESS| " checkpatch
2022-02-24 17:38 ` 0-day Robot [this message]

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=20220224173837.32031-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --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).