* Takashi Sakamoto o-takashi@sakamocchi.jp [2019-01-27 21:49 +0900]:
On Sun, Jan 27, 2019 at 09:14:02PM +0900, Takashi Sakamoto wrote:
Execution of unit test independent from actual sound device is one of my intention for the tests, and actually the they performs. Executables of the test include duplicated code of axfer for this intention. Please refer to 'axfer/test/Makefile.am'.
Of course, we can shorten the duration time by eliminating the range of parameters. Actually I've investigated to reduce iteration and reduce for the number of audio data frames in buffer by 6 options. But any reasonable explanation except for the duration time is required to be worth for it, IMO.
Well, what do you think to outbound your tests to i.e. $PREFIX/doc/examples to let the user decide whether to run them or not. A configure option to cancel the tests in the build process would be an option to be decided by the distribution maintainer.
The alsa-utils uses GNU Automake to implement test. As long as I know, any Makefile generated by GNU Automake doesn't run test unless 'check' target is given explicitly. https://www.gnu.org/software/automake/manual/html_node/Tests.html
Thereore, it depends on yout configuration of debhelper to execute the tests in building time of deb package. Please recheck your 'debian/rules' and adds appropriate directives to suppress execution of test for axfer (perhaps, 'override_dh_auto_test'). For example:
override_dh_auto_test: trueFor your information, alsa-utils includes no other test programs.
Or indicate test target explicitly in a directive of override_dh_auto_test:
override_dh_auto_test: # 'container-test' and 'mapper-test' for axfer take a long time. # They are designed to check robustness of internal # implementation of axfer and do not necessarily need to run in # a process of deb packaging. Let's suppress them. dh_auto_test -- TESTS=''
Wow, I never noticed the availability of dh_auto_test. Thanks alot!
Thanks for cooperation Elimar