TEST: .groupby().size() testing disabled due to pandas bug in 1.5.0

[vnlitvinov]

Modin version checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest released version of Modin.

• I have confirmed this bug exists on the main branch of Modin. (In order to do this you can follow this guide.)

Reproducible Example

import pandas as pd
arrays = [['Falcon', 'Falcon', 'Parrot', 'Parrot'], ['Captive', 'Wild', 'Captive', 'Wild']]
index = pd.MultiIndex.from_arrays(arrays, names=('Animal', 'Type'))
df = pd.DataFrame({'Max Speed': [390., 350., 30., 20.], 'stuff':[1, 2, 3, 4]}, index=index)
print(f'original df:\n{df}\n\n')
print(f'groupby1:\n{df.groupby(level=0,axis=1).size()}\n\n')
print(f'groupby2:\n{df.T.groupby(level=1,axis=1).size()}\n\n')

# simpler case
df = pd.DataFrame(
        {
            "col1": [0, 3, 2, 3],
            "col2": [4, 1, 6, 7],
            "col3": [3, 8, 2, 10],
            "col4": [1, 13, 6, 15],
            "col5": [-4, 5, 6, -7],
        }
    )
print(f'simple groupby:\n{df.groupby(axis=1, by=[1, 2, 3, 2, 1]).size()}')

Issue Description

Pandas bug: pandas-dev/pandas#48738

Expected Behavior

Tests should be run.

Error Logs

N/A, Modin seems to compute .groupby().size() correctly but due to pandas bug I had to disable related tests. Need to enable it back when moving to pandas where that bug is fixed.

Installed Versions

python -m modin --versions

INSTALLED VERSIONS
------------------
commit           : 3cccc0298eaa6a6a4bc03e7d1c1a8949184db0e0
python           : 3.8.13.final.0
python-bits      : 64
OS               : Windows
OS-release       : 10
Version          : 10.0.22000
machine          : AMD64
processor        : AMD64 Family 25 Model 80 Stepping 0, AuthenticAMD
byteorder        : little
LC_ALL           : None
LANG             : None
LOCALE           : Russian_Russia.1251

Modin dependencies
------------------
modin            : 0.15.0+181.g3cccc029.dirty
ray              : 2.0.0
dask             : 2022.9.0
distributed      : 2022.9.0
hdk              : None

pandas dependencies
-------------------
pandas           : 1.5.0
numpy            : 1.23.2
pytz             : 2022.2.1
dateutil         : 2.8.2
setuptools       : 65.3.0
pip              : 22.2.2
Cython           : None
pytest           : 7.1.3
hypothesis       : None
sphinx           : 5.1.1
blosc            : None
feather          : 0.4.1
xlsxwriter       : None
lxml.etree       : 4.9.1
html5lib         : None
pymysql          : None
psycopg2         : None
jinja2           : 3.1.2
IPython          : 8.4.0
pandas_datareader: None
bs4              : 4.11.1
bottleneck       : None
brotli           :
fastparquet      : 0.8.3
fsspec           : 2022.8.2
gcsfs            : None
matplotlib       : 3.2.2
numba            : None
numexpr          : 2.7.3
odfpy            : None
openpyxl         : 3.0.9
pandas_gbq       : 0.15.0
pyarrow          : 9.0.0
pyreadstat       : None
pyxlsb           : None
s3fs             : 2022.8.2
scipy            : 1.9.1
snappy           : None
sqlalchemy       : 1.4.40
tables           : 3.7.0
tabulate         : None
xarray           : 2022.6.0
xlrd             : 2.0.1
xlwt             : None
zstandard        : None
tzdata           : None

[mvashishtha]

Thanks @vnlitvinov. This issue is blocked on pandas releasing a point release that fixes the regression. We can fix this once pandas has released version 1.5.1 or higher.