#5736 closed enhancement (fixed)

kbd-2.8.0

Reported by: Bruce Dubbs Owned by: lfs-book
Priority: normal Milestone: 12.4
Component: Book Version: git
Severity: normal Keywords:
Cc:

Description

New minor version.

v2.8.0 
Changes

keymaps:

    Add Georgian font (LatCyrHebKa-16_GIA.psfu) and keymap (i386/qwerty/ge).
    Add new i386 azerty afnor keymap (i386/azerty/fr-afnor).
    Disable characters >=U+F000 in qwertz/de_alt_UTF-8.

libkeymap:

    Support KT_DEAD2 diacritics.
    Fix memory leaks.

utils:

    kbd_mode: support Disabled mode (K_OFF).

build-sys:

    configure: Restore the old behavior when using gzip.
    configure: Disable lex implementations other than flex.

other:

    tests: Fix tests on powerpc.
    tests: Add build and check on other architectures (x86_64, s390x, ppc64el).
    tests: Add valgrind check in unit tests.
    tests: Add sparse check and fix detected warnings.
    tests: Add tests to increase code coverage.
    tests: Check all distributed keymaps for loadability.

Change History (9)

comment:1 by Xi Ruoyao, 10 months ago

Almost all tests fail for me.

comment:2 by Xi Ruoyao, 10 months ago

It looks like most tests now unconditionally require valgrind.

comment:3 by Xi Ruoyao, 10 months ago

To run the tests w/o valgrind:

cat > tests/valgrind.sh << "EOF"
#!/bin/sh
shift
exec "$@" > stdout 2> stderr
EOF

comment:4 by Bruce Dubbs, 10 months ago

I was just looking at that. Should we add that to LFS or just say that the tests require valgrind? I lean toward the 2nd option.

comment:5 by Xi Ruoyao, 10 months ago

Both are fine to me.

comment:6 by Bruce Dubbs, 10 months ago

I built kbd on a full system and got:

## ------------- ##
## Test results. ##
## ------------- ##

ERROR: 47 tests were run,
5 failed unexpectedly.
4 tests were skipped.
## -------------------------- ##
## testsuite.log was created. ##
## -------------------------- ##

Please send 'tests/testsuite.log' and all information you think might help:

   To: <gladkov.alexey@gmail.com>
   Subject: [kbd 2.8.0] testsuite: 2 3 4 5 8 failed

Looking at tests/testsuite.log:

 NUM: FILE-NAME:LINE     TEST-GROUP-NAME
      KEYWORDS

   2: utils.at:12        loadkeys default keymap
      utils unittest
   3: utils.at:19        loadkeys prefer unicode with keymap file
      utils unittest
   4: utils.at:25        loadkeys prefer unicode with stdin
      utils unittest
   5: utils.at:31        loadkeys prefer unicode with stdin file
      utils unittest
   8: libcommon.at:19    test get console
      libcommon unittest

It looks like some test files are missing, but I'm not sure.

comment:7 by Bruce Dubbs, 10 months ago

I was testing over ssh when I got the above errors, so I copied the files to my workstation and got the same errors in a gui. However switching to a non-gui virtual terminal, no tests failed, but the 4 skipped tests were still there.

I will put this info in LFS with the recommendation that the tests not be run in the chroot environment.

Last edited 10 months ago by Bruce Dubbs (previous) (diff)

in reply to:  7 comment:8 by Xi Ruoyao, 10 months ago

Replying to Bruce Dubbs:

I was testing over ssh when I got the above errors, so I copied the files to my workstation and got the same errors in a gui. However switching to a non-gui virtual terminal, no tests failed, but the 4 skipped tests were still there.

I will put this info in LFS with the recommendation that the tests not be run in the chroot environment.

In a graphical terminal those tests seem requiring a root privilege, but in the Linux console they do not. I've no idea why.

comment:9 by Bruce Dubbs, 10 months ago

Resolution: fixed
Status: newclosed

Fixed in trunk from the gcc15 branch.

Note: See TracTickets for help on using tickets.