Backport PR pandas-dev#47020: CI: Move 32 bit Linux build to GHA

Author: mroeschke

.github/workflows/32-bit-linux.yml

@@ -0,0 +1,43 @@
+name: 32 Bit Linux
+
+on:
+  push:
+    branches:
+      - main
+      - 1.4.x
+  pull_request:
+    branches:
+      - main
+      - 1.4.x
+    paths-ignore:
+      - "doc/**"
+
+jobs:
+  pytest:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - name: Run 32-bit manylinux2014 Docker Build / Tests
+        run: |
+          docker pull quay.io/pypa/manylinux2014_i686
+          docker run --platform linux/386 -v $(pwd):/pandas quay.io/pypa/manylinux2014_i686 \
+          /bin/bash -xc "cd pandas && \
+          /opt/python/cp38-cp38/bin/python -m venv ~/virtualenvs/pandas-dev && \
+          . ~/virtualenvs/pandas-dev/bin/activate && \
+          python -m pip install --no-deps -U pip wheel 'setuptools<60.0.0' && \
+          pip install cython numpy python-dateutil pytz pytest pytest-xdist pytest-asyncio>=0.17 hypothesis && \
+          python setup.py build_ext -q -j2 && \
+          python -m pip install --no-build-isolation --no-use-pep517 -e . && \
+          export PANDAS_CI=1 && \
+          pytest -m 'not slow and not network and not clipboard and not single_cpu' pandas --junitxml=test-data.xml"
+
+      - name: Publish test results for Python 3.8-32 bit full Linux
+        uses: actions/upload-artifact@v3
+        with:
+          name: Test results
+          path: test-data.xml
+        if: failure()

.github/workflows/python-dev.yml

@@ -2,7 +2,7 @@
 # Unfreeze(by commentingthe if: false() condition) once the
 # next Python Dev version has released beta 1 and both Cython and numpy support it
 # After that Python has released, migrate the workflows to the
-# posix GHA workflows/Azure pipelines and "freeze" this file by
+# posix GHA workflows and "freeze" this file by
 # uncommenting the if: false() condition
 # Feel free to modify this comment as necessary.
 

README.md

@@ -10,7 +10,6 @@
 [![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.3509134.svg)](https://doi.org/10.5281/zenodo.3509134)
 [![Package Status](https://img.shields.io/pypi/status/pandas.svg)](https://pypi.org/project/pandas/)
 [![License](https://img.shields.io/pypi/l/pandas.svg)](https://github.com/pandas-dev/pandas/blob/main/LICENSE)
-[![Azure Build Status](https://dev.azure.com/pandas-dev/pandas/_apis/build/status/pandas-dev.pandas?branch=main)](https://dev.azure.com/pandas-dev/pandas/_build/latest?definitionId=1&branch=main)
 [![Coverage](https://codecov.io/github/pandas-dev/pandas/coverage.svg?branch=main)](https://codecov.io/gh/pandas-dev/pandas)
 [![Downloads](https://static.pepy.tech/personalized-badge/pandas?period=month&units=international_system&left_color=black&right_color=orange&left_text=PyPI%20downloads%20per%20month)](https://pepy.tech/project/pandas)
 [![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/pydata/pandas)

azure-pipelines.yml

@@ -443,13 +443,11 @@ library. This makes type checkers aware of the type annotations shipped with pan
 Testing with continuous integration
 -----------------------------------
 
-The pandas test suite will run automatically on `GitHub Actions <https://github.com/features/actions/>`__ and
-`Azure Pipelines <https://azure.microsoft.com/en-us/services/devops/pipelines/>`__
+The pandas test suite will run automatically on `GitHub Actions <https://github.com/features/actions/>`__
 continuous integration services, once your pull request is submitted.
 However, if you wish to run the test suite on a branch prior to submitting the pull request,
 then the continuous integration services need to be hooked to your GitHub repository. Instructions are here
-for `GitHub Actions <https://docs.github.com/en/actions/>`__ and
-`Azure Pipelines <https://docs.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops>`__.
+for `GitHub Actions <https://docs.github.com/en/actions/>`__.
 
 A pull-request will be considered for merging when you have an all 'green' build. If any tests are failing,
 then you will get a red 'X', where you can click through to see the individual failed tests.

doc/source/development/contributing_codebase.rst

@@ -649,7 +649,7 @@ def index_with_missing(request):
     """
 
     # GH 35538. Use deep copy to avoid illusive bug on np-dev
-    # Azure pipeline that writes into indices_dict despite copy
+    # GHA pipeline that writes into indices_dict despite copy
     ind = indices_dict[request.param].copy(deep=True)
     vals = ind.values
     if request.param in ["tuples", "mi-with-dt64tz-level", "multi"]:

pandas/conftest.py

@@ -71,7 +71,7 @@ def s3_base(worker_id):
             if is_platform_arm() or is_platform_mac() or is_platform_windows():
                 # NOT RUN on Windows/MacOS/ARM, only Ubuntu
                 # - subprocess in CI can cause timeouts
-                # - Azure pipelines/Github Actions do not support
+                # - Github Actions do not support
                 #   container services for the above OSs
                 # - CircleCI will probably hit the Docker rate pull limit
                 pytest.skip(

pandas/tests/io/conftest.py

@@ -21,7 +21,7 @@
 # TODO(GH#44584): Mark these as pytest.mark.single_cpu
 pytestmark = pytest.mark.skipif(
     is_ci_environment() and (is_platform_windows() or is_platform_mac()),
-    reason="On Azure CI, Windows can fail with "
+    reason="On GHA CI, Windows can fail with "
     "'Windows fatal exception: stack overflow' "
     "and MacOS can timeout",
 )

pandas/tests/window/test_numba.py

@@ -17,7 +17,7 @@
 # TODO(GH#44584): Mark these as pytest.mark.single_cpu
 pytestmark = pytest.mark.skipif(
     is_ci_environment() and (is_platform_windows() or is_platform_mac()),
-    reason="On Azure CI, Windows can fail with "
+    reason="On GHA CI, Windows can fail with "
     "'Windows fatal exception: stack overflow' "
     "and MacOS can timeout",
 )