| Summary: | dev-db/mariadb-5.5.39 dev-db/mysql-5.5.39 FEATURES=test - file INSTALL cannot copy file ".../work/mysql/mysql-test/./var-tests/tmp/mysqld.1.sock" to ".../image/usr/share/mysql/mysql-test/./var-tests/tmp/mysqld.1.sock". | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
| Component: | Current packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=476752 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
dev-db:mysql-5.5.39:20140930-100357.log.xz
dev-db:mariadb-5.5.39:20140930-202542.log.xz dev-db:mariadb-10.0.14:20141003-083731.log.xz dev-db:mysql-5.5.39:20141003-074340.log.xz mariadb-var-tests.patch |
||
|
Description
Jeroen Roovers (RETIRED)
2014-09-30 19:56:07 UTC
The real question is, why dev-db/mysql and dev-db/mariadb install hundreds of megabytes worth of test suite files? I see the same problem with dev-db/mariadb-5.5.39 . It isn't like bug #476752 where I'd run out of disk space: -- Installing: /mnt/alt/portage/dev-db/mariadb-5.5.39/image/usr/share/mysql/mysql-test/././var-tests/my.cnf -- Installing: /mnt/alt/portage/dev-db/mariadb-5.5.39/image/usr/share/mysql/mysql-test/././var-tests/tmp -- Installing: /mnt/alt/portage/dev-db/mariadb-5.5.39/image/usr/share/mysql/mysql-test/././var-tests/tmp/check-mysqld_1.log -- Installing: /mnt/alt/portage/dev-db/mariadb-5.5.39/image/usr/share/mysql/mysql-test/././var-tests/tmp/mysqld.1.sock CMake Error at mysql-test/cmake_install.cmake:36 (FILE): file INSTALL cannot copy file "/mnt/alt/portage/dev-db/mariadb-5.5.39/work/mysql/mysql-test/./var-tests/tmp/mysqld.1.sock" to "/mnt/alt/portage/dev-db/mariadb-5.5.39/image/usr/share/mysql/mysql-test/././var-tests/tmp/mysqld.1.sock". Call Stack (most recent call first): cmake_install.cmake:110 (INCLUDE) make: *** [install] Error 1 * ERROR: dev-db/mariadb-5.5.39::gentoo failed (install phase): * emake failed Created attachment 385872 [details]
dev-db:mariadb-5.5.39:20140930-202542.log.xz
Tests now cleanup the generated data when successful before install on all mysql providers. No, that's not a fix. Merely removing the test files means they get rebuilt in src_install(). Created attachment 385998 [details]
dev-db:mariadb-10.0.14:20141003-083731.log.xz
Created attachment 386000 [details]
dev-db:mysql-5.5.39:20141003-074340.log.xz
Comment on attachment 385998 [details]
dev-db:mariadb-10.0.14:20141003-083731.log.xz
I killed the test suite during the gdb section. This shouldn't (have) affect(ed) src_install().
Created attachment 386074 [details, diff]
mariadb-var-tests.patch
We could simply question the location of var-tests. Since cmake invariably installs whatever is found under mysql-test, we should probably use a path well outside the build system and then install the logs "${T}"/var-tests/log/*.log using different means.
Also, installing binaries in /usr/share probably isn't a good idea anyway. Or sockets.
(In reply to Jeroen Roovers from comment #9) > Created attachment 386074 [details, diff] [details, diff] > mariadb-var-tests.patch > > We could simply question the location of var-tests. Since cmake invariably > installs whatever is found under mysql-test, we should probably use a path > well outside the build system and then install the logs > "${T}"/var-tests/log/*.log using different means. Patch applied. If the logs need to be examined, the ebuild command will preserve them to be reviewed in ${T}. This is the official instructions and expected to be run this way. Otherwise, installing the tests will allow users to run it own their own terms. Where was this applied? |