Your message dated Thu, 14 Jan 2021 00:08:21 +0100
with message-id <[email protected]>
and subject line Re: djangorestframework FTBFS with pytest 6
has caused the Debian Bug report #977061,
regarding djangorestframework FTBFS with pytest 6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
977061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977061
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: djangorestframework
Version: 3.12.1-1
Severity: important
User: [email protected]
Usertags: pytest-v6
Hi,
djangorestframework FTBFS with pytest 6 in experimental.
The error log below has more details.
> =================================== FAILURES
> ===================================
> __________________ TestViewNamesAndDescriptions.test_markdown
> __________________
> tests/test_description.py:184: in test_markdown
> assert gte_21_match or lt_21_match
> E AssertionError: assert (False or False)
> =============================== warnings summary
> ===============================
> /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1148
> /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1148:
> PytestConfigWarning: Unknown config ini key: testspath
>
> self._warn_or_fail_if_strict("Unknown config ini key: {}\n".format(key))
>
> tests/test_serializer_nested.py::TestNestedSerializerWithMany::test_null_is_not_allowed_if_allow_null_is_not_set
> tests/test_serializer_nested.py::TestNestedSerializerWithMany::test_empty_not_allowed_if_allow_empty_is_set_to_false
> /<<PKGBUILDDIR>>/rest_framework/exceptions.py:77: DeprecationWarning:
> NotImplemented should not be used in a boolean context
> return r and self.code == other.code
>
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> =========================== short test summary info
> ============================
> SKIPPED [1] tests/test_model_serializer.py:445: condition: not postgres_fields
> SKIPPED [1] tests/test_model_serializer.py:430: condition: not postgres_fields
> SKIPPED [1] tests/test_model_serializer.py:462: condition: not postgres_fields
> SKIPPED [1] tests/test_model_serializer.py:487: no models.JSONField
> SKIPPED [1] tests/test_serializer_nested.py:325: psycopg2 is not installed
> SKIPPED [1] tests/test_serializer_nested.py:343: psycopg2 is not installed
> FAILED tests/test_description.py::TestViewNamesAndDescriptions::test_markdown
> ============ 1 failed, 1383 passed, 6 skipped, 3 warnings in 9.72s
> =============
> E: pybuild pybuild:353: test: plugin custom failed with: exit code=1:
> python3.9 /<<PKGBUILDDIR>>/runtests.py --nolint
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
> returned exit code 13
> make[1]: *** [debian/rules:31: override_dh_auto_test] Error 25
> make: *** [debian/rules:8: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
> 2
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
--- End Message ---
--- Begin Message ---
Hi Jonas,
On 13.01.21 23:03, Jonas Meurer wrote:
> I'm unable to reproduce the bug with pytest 6.0.2-2 from unstable. Also,
> according to ci.debian.net, the unit tests pass on all suites:
>
> https://ci.debian.net/packages/d/djangorestframework/
>
> Can you please provide further information on how to reproduce the bug?
> Or maybe it was a temporary error that's been resolved in the meantime?
I can't reproduce this either, odd. It must have been a temporary thing,
possibly cause by some dependency or so.
In any case, with CI passing, this is clearly no longer an issue,
therefore closing.
Thanks!
Christian
--- End Message ---
