Summary: | no generated_tests for CL | ||
---|---|---|---|
Product: | piglit | Reporter: | Igor Gnatenko <i.gnatenko.brain> |
Component: | infrastructure | Assignee: | Dylan Baker <baker.dylan.c> |
Status: | RESOLVED NOTABUG | QA Contact: | Piglit Mailing List <piglit> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Igor Gnatenko
2015-11-22 09:38:27 UTC
I can't replicate this bug, can you provide the cmake flags? Build log: https://kojipkgs.fedoraproject.org//packages/piglit/1.0.20151122/1.gitd095ba0.fc24/data/logs/x86_64/build.log In short: CFLAGS='-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic' /usr/bin/cmake -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 -DBUILD_SHARED_LIBS:BOOL=ON ../ -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_INSTALL_LIBDIR:PATH=lib64 I don't know what I did wrong the first time by I can replicate now. You're missing a configure option to get CL tests, they're off by default. add -DPIGLIT_BUILD_CL_TESTS=1 and you should be good to go. Let me know if that fixes it for you. I think we shouldn't install opencl profile also if we dont build ocl tests. I agree, and I was looking into it. In the meantime, did this fix the issue for you? It's still building. Yes, it fixed issue. I got some fails in test suite, but I will open other bugs. Cool. I'll mark this as closed then. |
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.