[Python-apps-team] Bug#868773: khal FTBFS: AssertionError: assert not OSError(6, 'No such device or address')

Christian Geier geier at lostpackets.de
Sat Oct 7 16:02:00 UTC 2017


Hi,
we (the khal developers) finally managed to reproduce this bug with the
help of docker, where /dev/tty does not exist. I would assume that the
environment where Debian runs these tests suffers from the very same
issue (can someone confirm this?). As these tests test reading from
stdin, I would advise you to skip those tests for now, as their failing
does not indicate a bug in khal, but a peculiarity in Debian's test
system.

Best regards,
Christian Geier

Quoting Guido Günther (2017-08-24 18:55:50)
> Hi,
> On Tue, Jul 18, 2017 at 03:41:33PM +0300, Adrian Bunk wrote:
> > Source: khal
> > Version: 1:0.9.6-1
> > Severity: serious
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=khal&arch=all&ver=1:0.9.6-1&stamp=1500381224&raw=0
> > 
> > ...
> > =================================== FAILURES ===================================
> > ____________________________ test_import_from_stdin ____________________________
> > 
> > runner = <tests.cli_test.CustomCliRunner object at 0x7faf8d02cf28>
> > 
> >     def test_import_from_stdin(runner):
> >         ics_data = 'This is some really fake icalendar data'
> >     
> >         with mock.patch('khal.controllers.import_ics') as mocked_import:
> >             runner = runner()
> >             result = runner.invoke(main_khal, ['import'], input=ics_data)
> >     
> > >       assert not result.exception
> > E       AssertionError: assert not OSError(6, 'No such device or address')
> > E        +  where OSError(6, 'No such device or address') = <Result OSError(6, 'No such device or address')>.exception
> > 
> > tests/cli_test.py:505: AssertionError
> > ________________________ test_printics_read_from_stdin _________________________
> > 
> > runner = <tests.cli_test.CustomCliRunner object at 0x7faf8cf7ce48>
> > 
> >     def test_printics_read_from_stdin(runner):
> >         runner = runner(command='printics')
> >         result = runner.invoke(main_khal, ['printics'], input=_get_text('cal_d'))
> > >       assert not result.exception
> > E       AssertionError: assert not OSError(6, 'No such device or address')
> > E        +  where OSError(6, 'No such device or address') = <Result OSError(6, 'No such device or address')>.exception
> > 
> > tests/cli_test.py:683: AssertionError
> > ========== 2 failed, 261 passed, 7 skipped, 3 xfailed in 9.52 seconds ==========
> > E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd /<<PKGBUILDDIR>>/.pybuild/pythonX.Y_3.6/build; python3.6 -m pytest tests
> > dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 3.5 returned exit code 13
> > debian/rules:26: recipe for target 'override_dh_auto_test' failed
> > make[1]: *** [override_dh_auto_test] Error 25
> 
> Any chance this gets fixed? It would be great to have a recent khal in
> unstable/testing.
>  -- Guido
> 



More information about the Python-apps-team mailing list