From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 415] encoding issue in when compiling ovs
Date: Tue, 03 Mar 2020 09:13:58 +0000 [thread overview]
Message-ID: <bug-415-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=415
Bug ID: 415
Summary: [dpdk-ci] encoding issue in when compiling ovs
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: job scripts
Assignee: ci@dpdk.org
Reporter: david.marchand@redhat.com
CC: dpdklab@iol.unh.edu
Target Milestone: ---
Caught for patchset: https://lab.dpdk.org/results/dashboard/patchsets/9781/
Log:
https://lab.dpdk.org/results/dashboard/results/results-uploads/test_runs/53f42c3a94994cb3b33ec9c64bf3fc83/log_upload_file/2020/2/dpdk_1f362c7a7b61_9781_2020-02-28_04-02-49_NA.zip
"""
An uncaught exception was raised. We may already know about the issue. If your
patch is not run again after one business day, feel free to contact us to let
us know.
Traceback (most recent call last):
File "/opt/dpdklab/dpdklab-ci/compile_ovs_with_podman.py", line 36, in
<module>
compile_ovs.build()
File "/opt/dpdklab/dpdklab-ci/compile_ovs_with_podman.py", line 26, in build
self.container_run(image, [
File "/opt/dpdklab/dpdklab-ci/ci.py", line 212, in container_run
self.run(cmd + args + [image], on_error=on_error)
File "/opt/dpdklab/dpdklab-ci/ci.py", line 105, in run
logging.info(line.decode('utf-8').strip(os.linesep))
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 96:
invalid continuation byte
"""
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-03-03 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 9:13 bugzilla [this message]
2020-03-03 18:57 ` [dpdk-ci] [Bug 415] encoding issue " bugzilla
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=bug-415-149@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@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).