Summary: | gnome-base/gconf: builds tests with FEATURES=-test | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | QA | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 226259 |
Description
Diego Elio Pettenò (RETIRED)
![]() Actually according to http://svn.gnome.org/svn/gconf/branches/gnome-2-18/Makefile.am http://svn.gnome.org/svn/gconf/branches/gnome-2-20/Makefile.am and now in trunk, I can't see where it could go into the tests folder. I checked out the repository to fix some other autofoo and I had to manually build tests with make -C tests like you said in your blog. Am I missing something ? And btw, we are not properly running tests in gconf it seems so it'll have to be fixed in our ebuild (see runtests.sh). Having to call make -C tests/ in src_test is NOT clean and acceptable in my eyes. actually, the only test that gets built is xml-test.c in gconf. The rest is /tests is not builded and can't be run because the test script is in fact missing from release tarballs. changing severity for easier searching. I have been reviewing gconf-2.32.0 build process and I don't see it's building tests/ when not needed, please recheck and, if still valid, try to provide a build.log to review. Thanks |