From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: less: update to 643.
Date: Mon, 14 Aug 2023 17:55:03 +0200 [thread overview]
Message-ID: <20230814155503.J72bLhHQy9bwVgC8XvPJho3bCPQ8jhrrVvibTy2VLbw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45600@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
New comment by Bnyro on void-packages repository
https://github.com/void-linux/void-packages/pull/45600#issuecomment-1677604465
Comment:
Less seems to use a different test suite using perl now, the error messages are not that helpful:
```
=> less-643_1: running do_check ...
if [ -x less ] && ./less -V | grep -q LESSTEST; then :; else make clean; make LESSTEST=1; fi
objdir=$(pwd); rflags=""; if [ -z "" ]; then rflags=-e; fi; cd ./lesstest && make && ./runtest $rflags -l "$objdir/less" lt
FAIL: utf8-2.txt (20 steps)
FAIL: chinese1 (29 steps)
if [ -x less ] && ./less -V | grep -q LESSTEST; then :; else make clean; make LESSTEST=1; fi
objdir=$(pwd); rflags=""; if [ -z "" ]; then rflags=-e; fi; cd ./lesstest && make && ./runtest $rflags -l "$objdir/less" lt
make[1]: Entering directory '/builddir/less-643/lesstest'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/builddir/less-643/lesstest'
DIFF utf8-2.txt on cmd #20 (. a)
FAIL: utf8-2.txt (20 steps)
ERR status 256 from /builddir/less-643/lesstest/lesstest -e -s '/builddir/less-643/lesstest/lt_screen' -t '/builddir/less-643/lesstest/lt/utf8-2.txt.lt' '/builddir/less-643/less'
DIFF chinese1 on cmd #29 (. a)
FAIL: chinese1 (29 steps)
ERR status 256 from /builddir/less-643/lesstest/lesstest -e -s '/builddir/less-643/lesstest/lt_screen' -t '/builddir/less-643/lesstest/lt/chinese1.lt' '/builddir/less-643/less'
RAN 13 tests with 2 errors
make: *** [Makefile:106: check] Error 1
=> ERROR: less-643_1: do_check: '${make_check_pre} ${make_cmd} ${makejobs} ${make_check_args} ${make_check_target}' exited with 2
=> ERROR: in do_check() at common/build-style/gnu-configure.sh:33
```
next prev parent reply other threads:[~2023-08-14 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 8:33 [PR PATCH] " Bnyro
2023-08-14 12:15 ` [PR REVIEW] " mhmdanas
2023-08-14 12:58 ` Bnyro
2023-08-14 12:59 ` Bnyro
2023-08-14 15:49 ` [PR PATCH] [Updated] " Bnyro
2023-08-14 15:53 ` Bnyro
2023-08-14 15:55 ` Bnyro [this message]
2023-08-20 14:08 ` [PR PATCH] [Merged]: " Duncaen
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=20230814155503.J72bLhHQy9bwVgC8XvPJho3bCPQ8jhrrVvibTy2VLbw@z \
--to=bnyro@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).