Summary: | TypeError: must be unicode, not str | ||
---|---|---|---|
Product: | piglit | Reporter: | Vinson Lee <vlee> |
Component: | infrastructure | Assignee: | Dylan Baker <baker.dylan.c> |
Status: | RESOLVED FIXED | QA Contact: | Piglit Mailing List <piglit> |
Severity: | normal | ||
Priority: | medium | Keywords: | regression |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Mac OS X (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | attachment-6191-0.html |
Description
Vinson Lee
2018-05-03 05:31:13 UTC
Created attachment 139314 [details] attachment-6191-0.html There's a patch for this on the list from me. I'm on mobile, please excuse autocorrect fail. On Wed, May 2, 2018, 22:31 <bugzilla-daemon@freedesktop.org> wrote: > Bug ID 106369 <https://bugs.freedesktop.org/show_bug.cgi?id=106369> > Summary TypeError: must be unicode, not str > Product piglit > Version unspecified > Hardware x86-64 (AMD64) > OS Mac OS X (All) > Status NEW > Keywords regression > Severity normal > Priority medium > Component infrastructure > Assignee baker.dylan.c@gmail.com > Reporter vlee@freedesktop.org > QA Contact piglit@lists.freedesktop.org > > Traceback (most recent call last): > File "tests/find_static_tests.py", line 74, in <module> > main() > File "tests/find_static_tests.py", line 69, in main > f.write(filename) > TypeError: must be unicode, not str > > ------------------------------ > You are receiving this mail because: > > - You are the assignee for the bug. > > commit 55207ea5154dfaa6d2c128124c50e3be4f9b6440 Author: Dylan Baker <dylan@pnwbakers.com> Date: Wed May 2 10:49:23 2018 -0700 find_static_tests.py: fix python2 compatibility Because python2 uses bytes, but python3 uses unicode. CC: Michel Dänzer <michel.daenzer@amd.com> Fixes: d42d909cd754d0e2c41eec60f3a1015f2d882b95 ("tests: Add script to find all hand written test files") Tested-by: Brian Paul <brianp@vmware.com> |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.