All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Elimar Riesebieter <riesebie@lxtec.de>
Cc: alsa-devel@alsa-project.org, Jordi Mallach <jordi@debian.org>
Subject: Re: alsa-utils 1.1.8: axfer tests take ages tu run.
Date: Sun, 27 Jan 2019 21:14:02 +0900	[thread overview]
Message-ID: <20190127121402.GA7056@workstation> (raw)
In-Reply-To: <20190127100304.4etta27wz6d7k65b@toy.home.lxtec.de>

Hi,

On Sun, Jan 27, 2019 at 11:03:04AM +0100, Elimar Riesebieter wrote:
> > I think it preferable to shorten the execution time of each unit test;
> > e.g. several minutes at maximum, however the purpose of unit test is to
> > detect bugs in advance and this program handles audio data frame between
> > the several types of buffer for I/O to sound device and the several
> > types of media container with combinations of many parameters. At
> > present it's reasonable to takes such long time to finish the tests.
> 
> This means you need a sound device on the building machine? Thats
> contra productive! I assume that at least our Debian buildd's don't
> have a sound device. How are those tests handled in that case? We
> need a properly solution for Linux distributions here!
 
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:
        true
```

For your information, alsa-utils includes no other test programs.


Thanks

Takashi Sakamoto

  reply	other threads:[~2019-01-27 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 14:49 alsa-utils 1.1.8: axfer tests take ages tu run Elimar Riesebieter
2019-01-26 16:04 ` Elimar Riesebieter
2019-01-27  3:44   ` Takashi Sakamoto
2019-01-27 10:03     ` Elimar Riesebieter
2019-01-27 12:14       ` Takashi Sakamoto [this message]
2019-01-27 12:49         ` Takashi Sakamoto
2019-01-27 13:18           ` Elimar Riesebieter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190127121402.GA7056@workstation \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=jordi@debian.org \
    --cc=riesebie@lxtec.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.