Bug#983326: rich: test failures with TERM=unknown

2021-02-28 Thread Sandro Tosi 
On Mon, 22 Feb 2021 13:27:20 +0100 Gianfranco Costamagna
 wrote:
> Hello, looks like the testsuite is failing with TERM=unknown, I don't really 
> know why, but calling dh_auto_test with TERM=linux seems to fix it.
>
> override_dh_auto_test:
> TERM=linux PYBUILD_SYSTEM=custom 
> PYBUILD_TEST_ARGS="PYTHONPATH=$(CURDIR) {interpreter} -m pytest" dh_auto_test
>
>
> I'm not adding the tag "patch" because some bug in the code probably exists.
>
> Example of failure:
> https://launchpadlibrarian.net/524437846/buildlog_ubuntu-hirsute-amd64.rich_9.11.0-1_BUILDING.txt.gz

as mentioned at
https://github.com/willmcgugan/rich/issues/1051#issuecomment-787529446
this is a Ubuntu-specific issue: why did you report it to debian,
where the package builds fine both on buildd and autopkgtest
infrastructures?

this is something you should report to launchpad and fix within ubuntu.

Bug#983326: rich: test failures with TERM=unknown

2021-02-23 Thread Sandro Tosi 
On Mon, 22 Feb 2021 13:27:20 +0100 Gianfranco Costamagna
 wrote:
> Source: rich
> Version: 9.11.0-1
> Severity: important
>
> Hello, looks like the testsuite is failing with TERM=unknown, I don't really 
> know why, but calling dh_auto_test with TERM=linux seems to fix it.

please follow up at
https://github.com/willmcgugan/rich/issues/1051#issuecomment-784097262
or reply to upstream questions here and i can echo them back on gh:

```
Rich will remove all ANSI control codes with TERM=unknown. The tests
aren't accounting for that, but AFAICT Rich is working as designed.

For the sake of reproducible tests, I could control the environment variables.

What was the reason for setting TERM=unknown ? Where you testing Rich
with the env var, or influencing the output of the test runner itself?
```

Bug#983326: rich: test failures with TERM=unknown

2021-02-22 Thread Gianfranco Costamagna 
Source: rich
Version: 9.11.0-1
Severity: important

Hello, looks like the testsuite is failing with TERM=unknown, I don't really 
know why, but calling dh_auto_test with TERM=linux seems to fix it.

override_dh_auto_test:
TERM=linux PYBUILD_SYSTEM=custom 
PYBUILD_TEST_ARGS="PYTHONPATH=$(CURDIR) {interpreter} -m pytest" dh_auto_test


I'm not adding the tag "patch" because some bug in the code probably exists.

Example of failure:
https://launchpadlibrarian.net/524437846/buildlog_ubuntu-hirsute-amd64.rich_9.11.0-1_BUILDING.txt.gz



APT_CONFIG=/var/lib/sbuild/apt.conf
DEB_BUILD_OPTIONS=parallel=4
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=buildd
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=build-PACKAGEBUILD-21056332
SCHROOT_CHROOT_NAME=build-PACKAGEBUILD-21056332
SCHROOT_COMMAND=env
SCHROOT_GID=2501
SCHROOT_GROUP=buildd
SCHROOT_SESSION_ID=build-PACKAGEBUILD-21056332
SCHROOT_UID=2001
SCHROOT_USER=buildd
SHELL=/bin/sh
TERM=unknown
USER=buildd
V=1

dpkg-buildpackage
-

dpkg-buildpackage: info: source package rich
dpkg-buildpackage: info: source version 9.11.0-1
dpkg-buildpackage: info: source distribution unstable
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using options from rich-9.11.0/debian/source/options: 
--extend-diff-ignore=^[^/]+.egg-info/
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:232: python3.9 setup.py clean 
running clean
removing '/<>/.pybuild/cpython3_3.9_rich/build' (and everything 
under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.9' does not exist -- can't clean it
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules build
dh build --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:232: python3.9 setup.py config 
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:232: /usr/bin/python3 setup.py build 
running build
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=/<> 
{interpreter} -m pytest" dh_auto_test
I: pybuild base:232: PYTHONPATH=/<> python3.9 -m pytest
= test session starts ==
platform linux -- Python 3.9.2, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
rootdir: /<>
collected 464 items

tests/test_align.py ..F. [  3%]
tests/test_ansi.py . [  3%]
tests/test_bar.py ...[  5%]
tests/test_block_bar.py  [  6%]
tests/test_box.py .. [  7%]
tests/test_card.py . [  7%]
tests/test_cells.py .[  7%]
tests/test_color.py  [ 11%]
tests/test_color_triplet.py ...  [ 11%]
tests/test_columns.py .  [ 12%]
tests/test_columns_align.py .[ 12%]
tests/test_console.py FFF.F..FFF.FFF.F.. [ 23%]
...FF.   [ 24%]
tests/test_constrain.py .[ 24%]
tests/test_containers.py [ 25%]
tests/test_control.py .. [ 25%]
tests/test_emoji.py  [ 26%]
tests/test_file_proxy.py ..  [ 27%]
tests/test_filesize.py ..[ 27%]
tests/test_highlighter.py .  [ 35%]
tests/test_inspect.py    [ 37%]
tests/test_jupyter.py .  [ 37%]
tests/test_layout.py ..  [ 37%]
tests/test_live.py .F.F.F[ 40%]
tests/test_live_render.py    [ 40%]
tests/test_log.py .. [ 41%]
tests/test_logging.py FF [ 41%]
tests/test_lrucache.py . [ 42%]
tests/test_markdown.py ..[ 42%]
tests/test_markdown_no_hyperlin