automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: g.singh@nxp.com, robot@bytheb.org
Subject: |FAILURE| pw145569 [v3] crypto/dpaa2_sec: rework debug code
Date: Thu, 10 Oct 2024 03:03:36 -0400	[thread overview]
Message-ID: <20241010070336.2565000-1-robot@bytheb.org> (raw)
In-Reply-To: <20241010060300.2308647-1-g.singh@nxp.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/11268602579
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-shared-aarch64" failed at step Run setup
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-shared-aarch64" at step Run setup
####################################################################################
          for chunk in chunks:
        File "/tmp/pip-standalone-pip-zfrgxjev/__env_pip__.zip/pip/_internal/cli/progress_bars.py", line 304, in _rich_progress_bar
          for chunk in iterable:
        File "/tmp/pip-standalone-pip-zfrgxjev/__env_pip__.zip/pip/_internal/network/utils.py", line 63, in response_chunks
          for chunk in response.raw.stream(
        File "/tmp/pip-standalone-pip-zfrgxjev/__env_pip__.zip/pip/_vendor/urllib3/response.py", line 576, in stream
          data = self.read(amt=amt, decode_content=decode_content)
        File "/tmp/pip-standalone-pip-zfrgxjev/__env_pip__.zip/pip/_vendor/urllib3/response.py", line 512, in read
          with self._error_catcher():
        File "/usr/lib/python3.10/contextlib.py", line 153, in __exit__
          self.gen.throw(typ, value, traceback)
        File "/tmp/pip-standalone-pip-zfrgxjev/__env_pip__.zip/pip/_vendor/urllib3/response.py", line 443, in _error_catcher
          raise ReadTimeoutError(self._pool, None, "Read timed out.")
      pip._vendor.urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Read timed out.
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× pip subprocess to install build dependencies did not run successfully.
│ exit code: 2
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-shared-aarch64" at step Run setup
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-10-10  7:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241010060300.2308647-1-g.singh@nxp.com>
2024-10-10  5:48 ` |SUCCESS| " qemudev
2024-10-10  5:52 ` qemudev
2024-10-10  6:03 ` checkpatch
2024-10-10  7:03 ` 0-day Robot [this message]
2024-10-10  8:03 ` 0-day Robot

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=20241010070336.2565000-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=g.singh@nxp.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).