While testing a new Percona release I experienced the following test failure: > sys_vars.innodb_buffer_pool_populate_basic w4 [ retry-fail ] Found warnings/errors in server log file! > Test ended at 2016-06-02 22:31:04 > line > 2016-06-02 23:31:04 58379 [Warning] InnoDB: Failed to set NUMA memory policy to MPOL_INTERLEAVE (error: Function not implement > ed). > 2016-06-02 23:31:04 58379 [Warning] InnoDB: Failed to set NUMA memory policy of buffer pool page frames to MPOL_INTERLEAVE (er > ror: Function not implemented). > 2016-06-02 23:31:04 58379 [Warning] InnoDB: Failed to set NUMA memory policy to MPOL_DEFAULT (error: Function not implemented) > . > ^ Found warnings in /var/tmp/portage/dev-db/percona-server-5.6.30.76.3/temp/var-tests/4/log/mysqld.1.err > ok > > - saving '/var/tmp/portage/dev-db/percona-server-5.6.30.76.3/temp/var-tests/4/log/sys_vars.innodb_buffer_pool_populate_basic/ > ' to '/var/tmp/portage/dev-db/percona-server-5.6.30.76.3/temp/var-tests/log/sys_vars.innodb_buffer_pool_populate_basic/' > > Test sys_vars.innodb_buffer_pool_populate_basic has failed 2 times, no more retries! > First I thought this is a problem in the new release however =dev-db/percona-server-5.6.29.76.2 now shows the same test failure on my system which passed last month. I reviewed my system changes and noticed that I unset CONFIG_NUMA in my kernel cfg last week. After re-enabling NUMA support the test passes again.
Not sure if I should ask upstream or if we should check kernel cfg in the ebuild and skip this test when NUMA is not set. PS: The test was introduced with https://github.com/percona/percona-server/commit/c005a86bad6e96c59d166ba388007aca89840c70
I am closing this as resolved: With percona-server-5.6.32.78.0 we introduced a new "numa" USE flag which will prevent automagic depedency on libnuma.so and also disable the test when running on a system without NUMA support: > commit abf9ebf84d9a073a1104a807d50357aacee3cc20 > Author: Thomas Deutschmann > Date: Fri Aug 26 16:14:58 2016 +0200 > > dev-db/percona-server: Bump to v5.6.32-78.0 > > Before this version percona-server automatically enabled NUMA support > when libnuma.so and headers were detected. > > Starting with this release you need to enable the new "numa" USE flag > if you want to have NUMA support. > > Please keep in mind that next to libnuma.so you also need kernel support > for NUMA. > > Gentoo-Bug: https://bugs.gentoo.org/584880 > > Package-Manager: portage-2.3.0
