Your message dated Tue, 1 Aug 2023 00:29:10 -0700
with message-id
<CAFe8ug_Kg20+GRv-uWO2e57Ok_Zi5EbMSMCcij1RzHd7=4b...@mail.gmail.com>
and subject line
has caused the Debian Bug report #975271,
regarding UnicodeDecodeError: 'utf-8' codec can't decode byte 0x89 in position
659: invalid start byte
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
975271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975271
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: piglit
Version: 0~git20200212-f4710c51b-1
Severity: normal
X-Debbugs-Cc: [email protected]
Hi,
$ piglit run sanity results/sanity
Traceback (most recent call last):
File "/usr/bin/piglit", line 178, in <module>
main()
File "/usr/bin/piglit", line 174, in main
sys.exit(runner(args))
File "/usr/lib/x86_64-linux-gnu/piglit/framework/exceptions.py", line 52, in
_inner
func(*args, **kwargs)
File "/usr/lib/x86_64-linux-gnu/piglit/framework/programs/run.py", line 362,
in run
backend.initialize(_create_metadata(
File "/usr/lib/x86_64-linux-gnu/piglit/framework/programs/run.py", line 268,
in _create_metadata
metadata['info']['system'] = core.collect_system_info()
File "/usr/lib/x86_64-linux-gnu/piglit/framework/core.py", line 182, in
collect_system_info
result[name] = out.decode('utf-8')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x89 in position 659:
invalid start byte
I try to find the invalid character (I have modified the
/usr/lib/x86_64-linux-gnu/piglit/framework/core.py to print all the out
to a file; but I report here the output before those modifications)
and I found that clinfo print a line with strange characters,
characters that you don't see if you call clinfo from the command line,
but you can see if you redirect the clinfo output to a file:
clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) P�|�%V
I look with and hex editor and I found that the string is
20 50 AD 7C EC 25 56 0A 20
This is a very strange output for clinfo, but I think that piglit will
need to work correctly
Ciao
Davide
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.1-dp-20201024 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages piglit depends on:
ii libc6 2.31-4
ii libegl1 1.3.2-1
ii libgcc-s1 10.2.0-16
ii libgl1 1.3.2-1
ii libstdc++6 10.2.0-16
ii libwaffle-1-0 1.6.1-3
ii libx11-6 2:1.6.12-1
ii ocl-icd-libopencl1 [libopencl1] 2.2.13-1
ii python3 3.8.6-1
ii python3-mako 1.1.3+ds1-1
ii python3-six 1.15.0-2
Versions of packages piglit recommends:
ii waffle-utils 1.6.1-3
piglit suggests no packages.
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/lib/x86_64-linux-gnu/piglit/framework/core.py (from
piglit package)
--- End Message ---
--- Begin Message ---
Closing. It sounds like Davide's clinfo bug led
to this being fixed.
-Jordan
--- End Message ---
