Bug 89349

Summary: Piglit make fail
Product: piglit Reporter: lu hua <huax.lu>
Component: testsAssignee: Dylan Baker <baker.dylan.c>
Status: VERIFIED DUPLICATE QA Contact: Piglit Mailing List <piglit>
Severity: normal    
Priority: high    
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description lu hua 2015-02-27 03:18:57 UTC
System Environment:
--------------------------
Piglit: c4585427913e4cb28994b4bfb11d49778273aa2c

Bug detailed description:
---------------------------
Piglit make fail.

Bisect shows: c4585427913e4cb28994b4bfb11d49778273aa2c is the first bad commit
commit c4585427913e4cb28994b4bfb11d49778273aa2c
Author:     Dylan Baker <baker.dylan.c@gmail.com>
AuthorDate: Thu Feb 19 14:12:05 2015 -0800
Commit:     Dylan Baker <baker.dylan.c@gmail.com>
CommitDate: Mon Feb 23 15:47:09 2015 -0800

    generated_tests: use future division in mako templates

    This provides consistency between the behavior of python2 and python3

    There are no changes in the generated files before and after this
    change, it simply ensures that things work the same for both versions of
    python.

    Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
    Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>

output:
[ 98%] Generating builtin_packing_tests.list
Traceback (most recent call last):
  File "/GFX/Test/Piglit/piglit/generated_tests/gen_builtin_packing_tests.py", line 48, in <module>
    TEMPLATES = template_dir(os.path.basename(os.path.splitext(__file__)[0]))
  File "/GFX/Test/Piglit/piglit/generated_tests/templates/__init__.py", line 86, in template_dir
    output_encoding='utf-8')
TypeError: __init__() got an unexpected keyword argument 'future_imports'
make[2]: *** [generated_tests/builtin_packing_tests.list] Error 1
make[1]: *** [generated_tests/CMakeFiles/gen-gl-tests.dir/all] Error 2
make: *** [all] Error 2
Comment 1 Vinson Lee 2015-02-27 07:43:53 UTC

*** This bug has been marked as a duplicate of bug 89347 ***

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.