From: ludo@gnu.org (Ludovic Courtès)
To: 27375@debbugs.gnu.org
Subject: bug#27375: Kodi tests take too long
Date: Thu, 15 Jun 2017 15:37:02 +0200 [thread overview]
Message-ID: <8760fx2wzl.fsf@gnu.org> (raw)
The ‘kodi-test’ program used during the test phase of Kodi takes quite a
bit of time, apparently spent scanning for /dev nodes that it won’t find
and waiting for them to show up, which never happens:
--8<---------------cut here---------------start------------->8---
open("/dev/snd/controlC15", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC15", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC16", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC16", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC17", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC17", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC18", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC18", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC19", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC19", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC20", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC20", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC21", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC21", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC22", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC22", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC23", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC23", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC24", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC24", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC25", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC25", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC26", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC26", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC27", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC27", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC28", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC28", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC29", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC29", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC30", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC30", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/snd/controlC31", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/dev/aloadC31", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(11, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x1d932e8, FUTEX_UNLOCK_PI_PRIVATE) = 0
nanosleep({tv_sec=1, tv_nsec=500000000}, ^Cstrace: Process 19805 detached
--8<---------------cut here---------------end--------------->8---
Probably that’s something done by alsa-lib. It would be good to disable
it though, because currently it takes 14937 seconds (more than 4
hours!), occupying a build slot.
Ludo’.
next reply other threads:[~2017-06-15 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 13:37 Ludovic Courtès [this message]
2018-02-25 17:49 ` bug#27375: Kodi tests take too long Marius Bakke
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=8760fx2wzl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27375@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.