Re: [dpdk-ci] |FAILURE| pw102055 [dpdk-dev] [PATCH v8 4/4] net/mlx5: support mempool registration

Re: [dpdk-ci] |FAILURE| pw102055 [dpdk-dev] [PATCH v8 4/4] net/mlx5: support mempool registration

[Dmitry Kozlyuk]

Hello,

I can't reproduce mempool_autotest failure locally.
Are test detailed logs published somewhere?
Or the only way is to wait for the community lab results?

> -----Original Message-----
> From: 0-day Robot <robot@bytheb.org>
> Sent: 18 октября 2021 г. 18:19
> To: test-report@dpdk.org
> Cc: Dmitry Kozlyuk <dkozlyuk@nvidia.com>; robot@bytheb.org
> Subject: |FAILURE| pw102055 [dpdk-dev] [PATCH v8 4/4] net/mlx5: support
> mempool registration
> 
> External email: Use caution opening links or attachments
> 
> 
> From: robot@bytheb.org
> 
> Test-Label: github-robot: build
> Test-Status: FAILURE
> http://patchwork.dpdk.org/patch/102055/
> 
> _github build: failed_
> Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1355221220
> Build Logs:
> -----------------------Summary of failed steps-----------------------
> "ubuntu-18.04-gcc-shared-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-doc+tests" at step Build and
> test
> ##########################################################################
> ##########
> 85/94 DPDK:fast-tests / thash_autotest        OK       0.17 s
> 86/94 DPDK:fast-tests / trace_autotest        OK       0.17 s
> 87/94 DPDK:fast-tests / telemetry_json_autotest  OK       0.17 s
> 88/94 DPDK:fast-tests / telemetry_data_autotest  OK       0.17 s
> 89/94 DPDK:fast-tests / ring_pmd_autotest     OK       0.17 s
> 90/94 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK       0.67 s
> 91/94 DPDK:fast-tests / bitratestats_autotest  OK       0.17 s
> 92/94 DPDK:fast-tests / latencystats_autotest  OK       0.17 s
> 93/94 DPDK:fast-tests / pdump_autotest        OK       5.24 s
> 94/94 DPDK:fast-tests / compressdev_autotest  SKIP     0.17 s
> 
> Ok:                   87
> 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-doc+tests" at step Build and
> test
> ##########################################################################
> ##########
> 
> 
> 
> 
> ##########################################################################
> ##########
> #### [Begin job log] "ubuntu-18.04-clang-shared-doc+tests" at step Build
> and test
> ##########################################################################
> ##########
> 85/94 DPDK:fast-tests / thash_autotest        OK       0.17 s
> 86/94 DPDK:fast-tests / trace_autotest        OK       0.17 s
> 87/94 DPDK:fast-tests / telemetry_json_autotest  OK       0.17 s
> 88/94 DPDK:fast-tests / telemetry_data_autotest  OK       0.17 s
> 89/94 DPDK:fast-tests / ring_pmd_autotest     OK       0.17 s
> 90/94 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK       0.77 s
> 91/94 DPDK:fast-tests / bitratestats_autotest  OK       0.17 s
> 92/94 DPDK:fast-tests / latencystats_autotest  OK       0.17 s
> 93/94 DPDK:fast-tests / pdump_autotest        OK       5.24 s
> 94/94 DPDK:fast-tests / compressdev_autotest  SKIP     0.17 s
> 
> Ok:                   87
> 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-----------------------------

Re: [dpdk-ci] |FAILURE| pw102055 [dpdk-dev] [PATCH v8 4/4] net/mlx5: support mempool registration

[Dmitry Kozlyuk]

> -----Original Message-----
> From: Dmitry Kozlyuk
> Sent: 18 октября 2021 г. 19:05
> To: ci@dpdk.org
> Subject: RE: |FAILURE| pw102055 [dpdk-dev] [PATCH v8 4/4] net/mlx5:
> support mempool registration
> 
> Hello,
> 
> I can't reproduce mempool_autotest failure locally.
> Are test detailed logs published somewhere?
> Or the only way is to wait for the community lab results?

Never mind, found the link in "Summary" section of the GitHub report.

Re: [dpdk-ci] |FAILURE| pw102055 [dpdk-dev] [PATCH v8 4/4] net/mlx5: support mempool registration

[Aaron Conole]

Dmitry Kozlyuk <dkozlyuk@oss.nvidia.com> writes:

>> -----Original Message-----
>> From: Dmitry Kozlyuk
>> Sent: 18 октября 2021 г. 19:05
>> To: ci@dpdk.org
>> Subject: RE: |FAILURE| pw102055 [dpdk-dev] [PATCH v8 4/4] net/mlx5:
>> support mempool registration
>> 
>> Hello,
>> 
>> I can't reproduce mempool_autotest failure locally.
>> Are test detailed logs published somewhere?
>> Or the only way is to wait for the community lab results?
>
> Never mind, found the link in "Summary" section of the GitHub report.

Glad you were able to find the link.

For future travelers, the Github Actions summary page contains archives
of the testlot.txt file.  Some scrolling might be required (I don't
think the interface is very user friendly in that regard).