Source: python-crontab
Version: 2.5.1-1
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6

Hi,


python-crontab FTBFS with pytest 6 in experimental. The pytest changelog
may offer clues as to why:

    https://docs.pytest.org/en/stable/changelog.html


The error log below has more details.

> I: pybuild base:232: python3.9 -m pytest
> ============================= test session starts 
> ==============================
> platform linux -- Python 3.9.1, pytest-6.0.2, py-1.9.0, pluggy-0.13.0
> rootdir: /<<PKGBUILDDIR>>
> collected 170 items
> 
> tests/test_compatibility.py ........s                                    [  
> 5%]
> tests/test_context.py .                                                  [  
> 5%]
> tests/test_croniter.py .....                                             [  
> 8%]
> tests/test_crontabs.py .....                                             [ 
> 11%]
> tests/test_description.py ss                                             [ 
> 12%]
> tests/test_enums.py ........                                             [ 
> 17%]
> tests/test_env.py ...........                                            [ 
> 24%]
> tests/test_equality.py ....                                              [ 
> 26%]
> tests/test_every.py .........                                            [ 
> 31%]
> tests/test_frequency.py .................                                [ 
> 41%]
> tests/test_interaction.py ...............................                [ 
> 60%]
> tests/test_log.py .......                                                [ 
> 64%]
> tests/test_range.py ........                                             [ 
> 68%]
> tests/test_removal.py ............                                       [ 
> 75%]
> tests/test_scheduler.py ...F.                                            [ 
> 78%]
> tests/test_system_cron.py ..........                                     [ 
> 84%]
> tests/test_usage.py ..................                                   [ 
> 95%]
> tests/test_utf8.py ........                                              
> [100%]
> 
> =================================== FAILURES 
> ===================================
> ____________________ SchedulerTestCase.test_04_schedule_ten 
> ____________________
> 
> self = <tests.test_scheduler.SchedulerTestCase 
> testMethod=test_04_schedule_ten>
> 
>     def test_04_schedule_ten(self):
>         """Every Ten Minutes"""
>>       self.assertSchedule("*/10 * * * *", 12, 1)
> 
> tests/test_scheduler.py:104: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> tests/test_scheduler.py:82: in assertSchedule
>     self.assertEqual(len(ret), result)
> E   AssertionError: 2 != 1
> =============================== warnings summary 
> ===============================
> tests/test_compatibility.py:111
>   /<<PKGBUILDDIR>>/tests/test_compatibility.py:111: DeprecationWarning: 
> invalid escape sequence \#
>     cron = crontab.CronTab(tab="""
> 
> <unknown>:111
> <unknown>:111
>   <unknown>:111: DeprecationWarning: invalid escape sequence \#
> 
> tests/test_interaction.py:51
>   /<<PKGBUILDDIR>>/tests/test_interaction.py:51: DeprecationWarning: invalid 
> escape sequence \%
>     RESULT_TAB = """# First Comment
> 
> <unknown>:51
>   <unknown>:51: DeprecationWarning: invalid escape sequence \%
> 
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> =========================== short test summary info 
> ============================
> FAILED tests/test_scheduler.py::SchedulerTestCase::test_04_schedule_ten - 
> Ass...
> ============= 1 failed, 166 passed, 3 skipped, 5 warnings in 0.92s 
> =============
> E: pybuild pybuild:353: test: plugin custom failed with: exit code=1: 
> python3.9 -m pytest
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 
> returned exit code 13
> make[1]: *** [debian/rules:9: override_dh_auto_test] Error 25
> make: *** [debian/rules:6: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'

Reply via email to