[Bug 2212443] New: python-pandas: FTBFS in Fedora 37
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2212443
Bug ID: 2212443
Summary: python-pandas: FTBFS in Fedora 37
Product: Fedora
Version: 37
URL: https://koschei.fedoraproject.org/package/python-panda
s
Status: NEW
Component: python-pandas
Assignee: jonathan(a)almalinux.org
Reporter: code(a)musicinmybrain.net
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
jonathan(a)almalinux.org, mail(a)kushaldas.in,
neuro-sig(a)lists.fedoraproject.org, orion(a)nwra.com,
python-packagers-sig(a)lists.fedoraproject.org,
sergio.pasra(a)gmail.com, tomspur(a)fedoraproject.org,
wfp5p(a)worldbroken.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Package python-pandas fails to build from source in Fedora 37.
Version-Release number of selected component (if applicable):
1.5.3-1.fc37
Steps to Reproduce:
koji build --scratch f37 python-pandas-1.5.3-1.fc37.src.rpm
Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/python-pandas
=================================== FAILURES
===================================
___________ test_construct_dask_float_array_int_dtype_match_ndarray
____________
[gw0] linux -- Python 3.11.3 /usr/bin/python3
@td.skip_if_no("dask")
def test_construct_dask_float_array_int_dtype_match_ndarray():
# GH#40110 make sure we treat a float-dtype dask array with the same
# rules we would for an ndarray
import dask.dataframe as dd
arr = np.array([1, 2.5, 3])
darr = dd.from_array(arr)
res = Series(darr)
expected = Series(arr)
tm.assert_series_equal(res, expected)
res = Series(darr, dtype="i8")
expected = Series(arr, dtype="i8")
tm.assert_series_equal(res, expected)
msg = "In a future version, passing float-dtype values containing NaN"
arr[2] = np.nan
> with tm.assert_produces_warning(FutureWarning, match=msg):
../../../BUILDROOT/python-pandas-1.5.3-1.fc37.x86_64/usr/lib64/python3.11/site-packages/pandas/tests/test_downstream.py:105:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib64/python3.11/contextlib.py:144: in __exit__
next(self.gen)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
def _assert_caught_no_extra_warnings(
*,
caught_warnings: Sequence[warnings.WarningMessage],
expected_warning: type[Warning] | bool | tuple[type[Warning], ...] |
None,
) -> None:
"""Assert that no extra warnings apart from the expected ones are
caught."""
extra_warnings = []
for actual_warning in caught_warnings:
if _is_unexpected_warning(actual_warning, expected_warning):
# GH#38630 pytest.filterwarnings does not suppress these.
if actual_warning.category == ResourceWarning:
# GH 44732: Don't make the CI flaky by filtering
SSL-related
# ResourceWarning from dependencies
unclosed_ssl = (
"unclosed transport
<asyncio.sslproto._SSLProtocolTransport",
"unclosed <ssl.SSLSocket",
)
if any(msg in str(actual_warning.message) for msg in
unclosed_ssl):
continue
# GH 44844: Matplotlib leaves font files open during the
entire process
# upon import. Don't make CI flaky if ResourceWarning
raised
# due to these open files.
if any("matplotlib" in mod for mod in sys.modules):
continue
extra_warnings.append(
(
actual_warning.category.__name__,
actual_warning.message,
actual_warning.filename,
actual_warning.lineno,
)
)
if extra_warnings:
> raise AssertionError(f"Caused unexpected warning(s): {repr(extra_warnings)}")
E AssertionError: Caused unexpected warning(s): [('RuntimeWarning',
RuntimeWarning('invalid value encountered in cast'),
'/builddir/build/BUILDROOT/python-pandas-1.5.3-1.fc37.x86_64/usr/lib64/python3.11/site-packages/pandas/core/dtypes/cast.py',
1836)]
../../../BUILDROOT/python-pandas-1.5.3-1.fc37.x86_64/usr/lib64/python3.11/site-packages/pandas/_testing/_warnings.py:192:
AssertionError
_______________________ test_xarray_cftimeindex_nearest
________________________
[gw0] linux -- Python 3.11.3 /usr/bin/python3
@td.skip_if_no("cftime")
@td.skip_if_no("xarray", "0.10.4")
def test_xarray_cftimeindex_nearest():
# https://github.com/pydata/xarray/issues/3751
import cftime
import xarray
times = xarray.cftime_range("0001", periods=2)
key = cftime.DatetimeGregorian(2000, 1, 1)
with tm.assert_produces_warning(
FutureWarning, match="deprecated", check_stacklevel=False
):
> result = times.get_loc(key, method="nearest")
E TypeError: CFTimeIndex.get_loc() got an unexpected keyword argument
'method'
../../../BUILDROOT/python-pandas-1.5.3-1.fc37.x86_64/usr/lib64/python3.11/site-packages/pandas/tests/test_downstream.py:131:
TypeError
These new errors were caused by dependency updates; numpy 1:1.24.3-1.fc37 and
python-xarray 2023.4.2-2.fc37 are likely involved.
I’m not inclined to put a lot of effort into backporting changes from a more
recent version of Pandas. If we want to fix the FTBFS, it may be just to skip
these two tests and pretend everything is OK.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2212443
4 months
[Bug 2211786] New: [abrt] cinnamon: __init__(): Gtk.py:519:__init__:RuntimeError: Gtk couldn't be initialized. Use Gtk.init_check() if you want to handle this case.
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2211786
Bug ID: 2211786
Summary: [abrt] cinnamon: __init__():
Gtk.py:519:__init__:RuntimeError: Gtk couldn't be
initialized. Use Gtk.init_check() if you want to
handle this case.
Product: Fedora
Version: 37
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:594c08851c7c6aff59b74e76fb39c2b26a27058a;
Component: cinnamon
Assignee: leigh123linux(a)googlemail.com
Reporter: gui1ty(a)penguinpee.nl
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
leigh123linux(a)googlemail.com, miketwebster(a)gmail.com,
riehecky(a)fnal.gov
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
cinnamon-5.6.8-2.fc37
Additional info:
reporter: libreport-2.17.10
cgroup: 0::/user.slice/user-1000.slice/session-28.scope
cmdline: /usr/bin/python3 /usr/bin/cinnamon-close-dialog 50331668
Desktop
crash_function: __init__
exception_type: RuntimeError
executable: /usr/bin/cinnamon-close-dialog
interpreter: python3-3.11.3-2.fc37.x86_64
kernel: 6.2.14-200.fc37.x86_64
runlevel: N 5
type: Python3
uid: 1000
Truncated backtrace:
Gtk.py:519:__init__:RuntimeError: Gtk couldn't be initialized. Use
Gtk.init_check() if you want to handle this case.
Traceback (most recent call last):
File "/usr/bin/cinnamon-close-dialog", line 98, in <module>
dialog = CloseDialog(args.xid, args.message)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/bin/cinnamon-close-dialog", line 29, in __init__
XApp.GtkWindow.__init__(self,
File "/usr/lib/python3.11/site-packages/gi/overrides/Gtk.py", line 519, in
__init__
raise RuntimeError(
RuntimeError: Gtk couldn't be initialized. Use Gtk.init_check() if you want to
handle this case.
Local variables in innermost frame:
self: <__main__.CloseDialog object at 0x7fecac30de80 (uninitialized at
0x(nil))>
args: ()
kwargs: {'resizable': False, 'modal': True, 'type_hint': <enum
GDK_WINDOW_TYPE_HINT_DIALOG of type Gdk.WindowTypeHint>}
Potential duplicate: bug 1750018
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2211786
4 months