Source: djangorestframework
Version: 3.12.1-1
Severity: serious
X-Debbugs-CC: debian-ci@lists.debian.org, python-django@packages.debian.org
Tags: sid bookworm
User: debian-ci@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-django
Dear maintainer(s),
With a recent upload of python-django the autopkgtest of
djangorestframework fails in testing when that autopkgtest is run with
the binary packages of python-django from unstable. It passes when run
with only packages from testing. In tabular form:
pass fail
python-django from testing 2:3.2.7-4
djangorestframework from testing 3.12.1-1
versioned deps [0] from testing from unstable
all others from testing from testing
I copied some of the output at the bottom of this report. It seems to me
that the error handling got improved.
Currently this regression is blocking the migration of python-django to
testing [1]. Of course, python-django shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in python-django was intended and your package needs to update to
the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python-django should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
python-django/2:3.2.7-4. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=python-django
https://ci.debian.net/data/autopkgtest/testing/amd64/d/djangorestframework/15232622/log.gz
=================================== FAILURES
===================================
_____
TestNaiveDayLightSavingTimeTimeZoneDateTimeField.test_invalid_inputs _____
self =
<tests.test_fields.TestNaiveDayLightSavingTimeTimeZoneDateTimeField
object at 0x7fe05e8d3b80>
def test_invalid_inputs(self):
"""
Ensure that invalid values raise the expected validation error.
"""
for input_value, expected_failure in get_items(self.invalid_inputs):
with pytest.raises(serializers.ValidationError) as exc_info:
self.field.run_validation(input_value)
> assert exc_info.value.detail == expected_failure, \
'input value: {}'.format(repr(input_value))
E AssertionError: input value: '2017-03-12T02:30:00'
E assert [ErrorDetail(...de='invalid')] == ['Invalid
dat...a/New_York".']
E At index 0 diff: ErrorDetail(string='Datetime has wrong
format. Use one of these formats instead:
YYYY-MM-DDThh:mm[:ss[.uuuuuu]][+HH:MM|-HH:MM|Z].', code='invalid') !=
'Invalid datetime for the timezone "America/New_York".'
E Use -v to get the full diff
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature