[dpdk-ci] [Bug 415] encoding issue in when compiling ovs

[dpdk-ci] [Bug 415] encoding issue in when compiling ovs

[bugzilla]

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.

[dpdk-ci] [Bug 415] encoding issue when compiling ovs

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=415

Brandon Lo (blo@iol.unh.edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|IN_PROGRESS                 |RESOLVED

--- Comment #1 from Brandon Lo (blo@iol.unh.edu) ---
Rerunning the test does not recreate the issue, so I'm unsure as to what could
have caused it. I'm assuming this is a pretty uncommon issue. I resolved this
by catching the exception and logging it without a decode call since it is a
string returned by subprocess.

-- 
You are receiving this mail because:
You are the assignee for the bug.