delta/util-linux.git/tests/ts/col, branch master

tests: wrap $TS_{TOPDIR,SELF} in "." cmdline with double quote chars

2022-11-23T07:09:48+00:00

The command lines used for this change:

  $ cd tests/ts
  $ sed  -i -e 's|. $TS_SELF/|. "$TS_SELF"/|'  $(grep --exclude='*~' -lr -e '^\. \$TS_SELF/')
  $ sed -i -e 's|. $TS_TOPDIR/functions.sh|. "$TS_TOPDIR"/functions.sh|'  $(grep --exclude='*~' -lr -e '^\. \$TS_TOPDIR/functions.sh')

Signed-off-by: Masatake YAMATO

tests: split several tests into subtests

2021-10-14T10:33:45+00:00

tests: split test into subtest

2021-10-04T14:46:22+00:00

col: make input to tolerate invalid wide characters

2020-12-02T22:12:32+00:00

The getwchar(3) will choke and exit if invalid character is encountered.
This change will make col(1) to print broken multibyte characters as
\x{hex} string.

Reported-by: Vitaly Lipatov 
Addresses: https://github.com/karelzak/util-linux/issues/1198
Signed-off-by: Sami Kerola

col: add more tests

2020-09-11T19:55:01+00:00

With these tests coverage is about 89%.

The ts_run is added to ensure ASAN_OPTIONS and UBSAN_OPTIONS are set
correctly when the tests run.

Reference: https://github.com/karelzak/util-linux/pull/1115#issuecomment-670140224
Signed-off-by: Sami Kerola

col: fix output when first line does not have newline character

2020-06-20T21:17:30+00:00

Commit I made while back and has been part of util-linux v2.30 to v2.35 made
col(1) not to output anything when first line did not have newline character.

    printf "gone from output" | col

This commit fixes the issue.  Admittedly the col source code is unnecessarily
hard to work with.  It could be a good idea to refactor the col(1) as low
priority task, Assuming refactoring is done the first commit to get that done
should add tests that exhaust all possible input handling including all command
line option directives.

Addresses: https://github.com/karelzak/util-linux/issues/422
Fixes: b6b5272b03ea9d3fa15601801d4d0f76ea4440f1
Signed-off-by: Sami Kerola

tests: (col) avoid hardcoding of errno string

2019-08-27T07:37:01+00:00

The col/multibyte test has a hardcoded error string as part of its
expected output that is returned by glibc's strerror(3P) function. Even
though many of these strings are the same across libc implementations,
they are not standardiced and some are certainly different. One example
is the string for EILSEQ on musl libc.

To fix this, we introduce a new test helper "test_strerror". The helper
can be invoked with an error code like "EILSEQ", which will cause it to
print out the the respective error message for that code. Note that
"test_strerror" cannot act on the error's value (e.g. 84 for EILSEQ), as
these aren't standardized either. Instead, we thus need to have an array
of the error's string representation ("EILSEQ") to its respective error
code (the define EILSEQ). The array can trivially be extended as
required, thus it is only sparsely populated with EILSEQ right now.

To fix the col/multibyte test, we introduce a call to sed(1) to replace
the strerror(3P) message from EILSEQ with "EILSEQ". Furthermore, as
we're running tests with the POSIX locale by default which treats all
bytes as valid multibyte sequences, we have to change to the C.UTF-8
locale instead to actually get an error.

Signed-off-by: Patrick Steinhardt

tests: check commands needed for running a test exist

2014-03-07T10:52:57+00:00

Signed-off-by: Sami Kerola 
Signed-off-by: Karel Zak

tests: avoid executing dirname(1) command

2014-02-17T12:55:41+00:00

Bash parameter expansion does the same thing.

Signed-off-by: Sami Kerola

rename util-linux-ng back to util-linux

2010-11-30T10:41:59+00:00

Signed-off-by: Karel Zak