Source: pandas
Version: 1.3.5+dfsg-6
Severity: serious
X-Debbugs-CC: nu...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:numpy

Dear maintainer(s),

With a recent upload of numpy the autopkgtest of xmds2 fails in testing on i386 when that autopkgtest is run with the binary packages of numpy from unstable. It passes when run with only packages from testing. In tabular form:

                       pass            fail
numpy                  from testing    1:1.23.5-2
xmds2                  from testing    1.3.5+dfsg-6
all others             from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of numpy to testing [1]. Of course, numpy shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in numpy 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 numpy 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

[1] https://qa.debian.org/excuses.php?package=numpy

https://ci.debian.net/data/autopkgtest/testing/i386/p/pandas/29451939/log.gz

=================================== FAILURES =================================== _ TestDateRanges.test_date_range_int64_overflow_stride_endpoint_different_signs _

self = <pandas.tests.indexes.datetimes.test_date_range.TestDateRanges object at 0xebec9538>

    @pytest.mark.slow
def test_date_range_int64_overflow_stride_endpoint_different_signs(self):
        # cases where stride * periods overflow int64 and stride/endpoint
        #  have different signs
        start = Timestamp("2262-02-23")
        end = Timestamp("1969-11-14")

        expected = date_range(start=start, end=end, freq="-1H")
        assert expected[0] == start
        assert expected[-1] == end

        dti = date_range(end=end, periods=len(expected), freq="-1H")
>       tm.assert_index_equal(dti, expected)
E       AssertionError: Index are different
E
E       Index length are different
E       [left]:  0, DatetimeIndex([], dtype='datetime64[ns]', freq='-1H')
E [right]: 2562049, DatetimeIndex(['2262-02-23 00:00:00', '2262-02-22 23:00:00',
E                      '2262-02-22 22:00:00', '2262-02-22 21:00:00',
E                      '2262-02-22 20:00:00', '2262-02-22 19:00:00',
E                      '2262-02-22 18:00:00', '2262-02-22 17:00:00',
E                      '2262-02-22 16:00:00', '2262-02-22 15:00:00',
E                      ...
E                      '1969-11-14 09:00:00', '1969-11-14 08:00:00',
E                      '1969-11-14 07:00:00', '1969-11-14 06:00:00',
E                      '1969-11-14 05:00:00', '1969-11-14 04:00:00',
E                      '1969-11-14 03:00:00', '1969-11-14 02:00:00',
E                      '1969-11-14 01:00:00', '1969-11-14 00:00:00'],
E                     dtype='datetime64[ns]', length=2562049, freq='-1H')

/usr/lib/python3/dist-packages/pandas/tests/indexes/datetimes/test_date_range.py:161: AssertionError =============================== warnings summary ===============================

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to