From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: haijie1@huawei.com, robot@bytheb.org
Subject: |FAILURE| pw142118 [PATCH] net/hns3: support more VLAN fields matching
Date: Wed, 3 Jul 2024 23:04:10 -0400 [thread overview]
Message-ID: <20240704030410.1333025-1-robot@bytheb.org> (raw)
In-Reply-To: <20240704021538.836403-1-haijie1@huawei.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/142118/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9787548597
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-ppc64le" failed at step Set up job
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-ppc64le" at step Set up job
####################################################################################
Actions: write
Attestations: write
Checks: write
Contents: write
Deployments: write
Discussions: write
Issues: write
Metadata: read
Packages: write
Pages: write
PullRequests: write
RepositoryProjects: write
SecurityEvents: write
Statuses: write
##[endgroup]
Secret source: Actions
Prepare workflow directory
Prepare all required actions
Getting action download info
Download action repository 'actions/checkout@v4' (SHA:692973e3d937129bcbf40652eb9f2f61becf3332)
##[warning]Failed to download action 'https://api.github.com/repos/actions/checkout/tarball/692973e3d937129bcbf40652eb9f2f61becf3332'. Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
##[warning]Back off 14.904 seconds before retry.
##[warning]Failed to download action 'https://api.github.com/repos/actions/checkout/tarball/692973e3d937129bcbf40652eb9f2f61becf3332'. Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
##[warning]Back off 22.093 seconds before retry.
##[error]Connection reset by peer (api.github.com:443)
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-ppc64le" at step Set up job
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2024-07-04 3:04 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240704021538.836403-1-haijie1@huawei.com>
2024-07-04 1:49 ` |SUCCESS| " qemudev
2024-07-04 1:53 ` qemudev
2024-07-04 2:16 ` checkpatch
2024-07-04 3:04 ` 0-day Robot [this message]
2024-07-04 10:58 ` |PENDING| pw142118 [PATCH] net/hns3: support more VLAN fields matchi dpdklab
2024-07-04 11:00 ` |SUCCESS| " dpdklab
2024-07-04 11:04 ` dpdklab
2024-07-04 11:08 ` dpdklab
2024-07-04 11:09 ` dpdklab
2024-07-04 11:11 ` dpdklab
2024-07-04 11:22 ` dpdklab
2024-07-04 12:24 ` dpdklab
2024-07-04 14:12 ` |PENDING| " dpdklab
2024-07-04 14:28 ` dpdklab
2024-07-04 14:28 ` dpdklab
2024-07-04 14:34 ` dpdklab
2024-07-04 14:36 ` dpdklab
2024-07-04 14:38 ` dpdklab
2024-07-04 14:42 ` dpdklab
2024-07-04 14:46 ` dpdklab
2024-07-04 14:48 ` dpdklab
2024-07-04 14:49 ` dpdklab
2024-07-04 14:53 ` dpdklab
2024-07-04 14:55 ` dpdklab
2024-07-04 14:56 ` dpdklab
2024-07-04 14:56 ` dpdklab
2024-07-04 14:57 ` dpdklab
2024-07-04 15:09 ` |SUCCESS| " dpdklab
2024-07-04 19:44 ` |PENDING| " dpdklab
2024-07-04 19:52 ` |SUCCESS| " dpdklab
2024-07-04 20:26 ` dpdklab
2024-07-04 22:59 ` dpdklab
2024-07-04 23:04 ` dpdklab
2024-07-04 23:09 ` dpdklab
2024-07-04 23:14 ` dpdklab
2024-07-04 23:34 ` dpdklab
2024-07-05 0:55 ` |PENDING| " dpdklab
2024-07-05 1:00 ` dpdklab
2024-07-05 1:12 ` |SUCCESS| " dpdklab
2024-07-05 1:19 ` |PENDING| " dpdklab
2024-07-05 1:53 ` dpdklab
2024-07-05 1:54 ` |SUCCESS| " dpdklab
2024-07-05 2:02 ` |PENDING| " dpdklab
2024-07-05 2:46 ` dpdklab
2024-07-05 4:33 ` dpdklab
2024-07-05 6:05 ` dpdklab
2024-07-05 9:50 ` dpdklab
2024-07-05 9:55 ` dpdklab
2024-07-05 9:59 ` dpdklab
2024-07-05 10:03 ` dpdklab
2024-07-05 10:03 ` dpdklab
2024-07-05 10:12 ` dpdklab
2024-07-05 10:12 ` dpdklab
2024-07-05 10:17 ` dpdklab
2024-07-05 10:19 ` dpdklab
2024-07-05 10:21 ` dpdklab
2024-07-05 10:21 ` dpdklab
2024-07-05 10:25 ` dpdklab
2024-07-05 10:28 ` |SUCCESS| " dpdklab
2024-07-05 12:04 ` |PENDING| " dpdklab
2024-07-05 12:04 ` dpdklab
2024-07-05 12:05 ` dpdklab
2024-07-05 12:07 ` dpdklab
2024-07-05 12:10 ` dpdklab
2024-07-05 12:13 ` dpdklab
2024-07-05 12:13 ` dpdklab
2024-07-05 12:18 ` dpdklab
2024-07-05 12:22 ` dpdklab
2024-07-05 12:29 ` dpdklab
2024-07-05 12:29 ` dpdklab
2024-07-05 12:31 ` dpdklab
2024-07-05 12:34 ` dpdklab
2024-07-05 12:35 ` dpdklab
2024-07-05 12:38 ` dpdklab
2024-07-05 12:43 ` dpdklab
2024-07-05 12:44 ` dpdklab
2024-07-05 12:50 ` |SUCCESS| " dpdklab
2024-07-05 12:59 ` |PENDING| " dpdklab
2024-07-05 13:06 ` dpdklab
2024-07-05 13:35 ` dpdklab
2024-07-05 13:36 ` dpdklab
2024-07-05 13:40 ` dpdklab
2024-07-05 13:43 ` dpdklab
2024-07-05 13:46 ` dpdklab
2024-07-05 13:48 ` dpdklab
2024-07-05 13:56 ` dpdklab
2024-07-05 14:05 ` dpdklab
2024-07-05 14:14 ` dpdklab
2024-07-05 14:16 ` dpdklab
2024-07-05 14:17 ` dpdklab
2024-07-05 14:19 ` dpdklab
2024-07-05 14:22 ` dpdklab
2024-07-05 14:23 ` dpdklab
2024-07-05 14:24 ` dpdklab
2024-07-05 14:30 ` dpdklab
2024-07-05 14:35 ` dpdklab
2024-07-05 14:36 ` dpdklab
2024-07-05 14:43 ` dpdklab
2024-07-05 14:48 ` dpdklab
2024-07-05 14:51 ` dpdklab
2024-07-05 14:57 ` dpdklab
2024-07-05 14:58 ` |SUCCESS| " dpdklab
2024-07-05 15:12 ` |PENDING| " dpdklab
2024-07-05 15:16 ` dpdklab
2024-07-05 15:18 ` dpdklab
2024-07-05 15:21 ` dpdklab
2024-07-05 15:24 ` dpdklab
2024-07-05 15:26 ` dpdklab
2024-07-05 15:51 ` dpdklab
2024-07-05 15:52 ` |SUCCESS| " dpdklab
2024-07-05 15:54 ` dpdklab
2024-07-05 19:26 ` dpdklab
2024-07-06 10:48 ` dpdklab
2024-07-06 12:20 ` dpdklab
2024-07-06 12:49 ` 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=20240704030410.1333025-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=haijie1@huawei.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).