Using /var/tmp/portage/dev-util/cgdb-0.7.0/work/cgdb-0.7.0/test/config/unix.exp as tool-and-target-specific interface file. Running /var/tmp/portage/dev-util/cgdb-0.7.0/work/cgdb-0.7.0/test/kui.base/basic.exp ... FAIL: timeout testing map from mapping file FAIL: timeout test simple map FAIL: timeout test simple partial matching map FAIL: timeout test map that is a subset of another map ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_abi32+64-test_20180501-232814 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) emerge -qpv dev-util/cgdb [ebuild N ] dev-util/cgdb-0.7.0 USE="{test}" ABI_X86="32 (64) (-x32)"
Created attachment 530008 [details] emerge-info.txt
Created attachment 530010 [details] dev-util:cgdb-0.7.0:20180505-164610.log
Created attachment 530012 [details] emerge-history.txt
Created attachment 530014 [details] environment
Created attachment 530016 [details] etc.portage.tbz2
Created attachment 530018 [details] logs.tbz2
Created attachment 530020 [details] temp.tbz2
Thank you Toralf, I am actually glad to see other test failure, I hope I can reproduce that one or that it is linked to the previous one (https://bugs.gentoo.org/630512). I'll check that this week hopefully.
Could it be coming from the sandboxing of the tinderbox ? The tests failing are emulating key presses. I'm not much used to dejagnu, anyone who might tell me what this line [1] relies on is welcome. It is the function failing to emulate key presses, that much I know but what it actually does, I have no idea. File where the "kui_prompt" are called [2] [1] https://github.com/cgdb/cgdb/blob/v0.7.0/test/config/unix.exp#L13 [2] https://github.com/cgdb/cgdb/blob/v0.7.0/test/kui.base/basic.exp
I won't claim myself to be a dejagnu expert but I can tell you that's single worst framework ever invented. To get (most of) bash-completion tests working, I needed to run them inside dtach to get a backing VT. Feel free to try to copy the code from app-shells/bash-completion and see if it helps.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6a058bfd996599ead9fe3e50f802ccd088bd0a73 commit 6a058bfd996599ead9fe3e50f802ccd088bd0a73 Author: nado <nado@troglodyte.be> AuthorDate: 2018-07-19 15:57:25 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2019-04-03 06:50:07 +0000 dev-util/cgdb: run tests in `dtach` + EAPI bump cgdb needs interactive shell for testing its ncurses UI Closes: https://bugs.gentoo.org/654986 Package-Manager: Portage-2.3.43, Repoman-2.3.10 Signed-off-by: Corentin `nado` Pazdera <nado@troglodyte.be> Closes: https://github.com/gentoo/gentoo/pull/9288 Signed-off-by: Michał Górny <mgorny@gentoo.org> .../{cgdb-0.7.0.ebuild => cgdb-0.7.0-r1.ebuild} | 31 ++++++++++++++++---- dev-util/cgdb/cgdb-9999.ebuild | 33 +++++++++++++++++----- 2 files changed, 51 insertions(+), 13 deletions(-)
