tree 32d6eac9ba118606e65cc717e172d1c07a91c1fb
parent 4a1f619d1e712c2f20743a89ee1249730752e141
author Scott Todd <scott.todd0@gmail.com> 1722895667 -0700
committer GitHub <noreply@github.com> 1722895667 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJmsU0zCRC1aQ7uu5UhlAAAv6QQAIlDXo4T31GgrSEDLmdhNQth
 MFj3D1+BwCTPNoua6cYaq/G/BP2x86jsqYbV+V6DaOgRSIC62/hH4cbNP/BEmEKm
 oBxlgZMe3AF7Lc85HEAN+bbvUtTWSzYHoIhMUWsV65KUi4CsuFaHMPSWKygSBWcH
 AKPZM2h2mPdHPcfOmTj9hRjg9o+pJCe4V6i4Rz9W/SXMR2QGvAW+MTUEbFEWitdh
 xmRvtbeimgm5uoh7JjIL0UlpDX3eZaCXb6yZz8vPZpHVnZWKdvhEwbBJCe1WEr5d
 RxpN3x1aW88BY+PXsdLy3RxNLDef+UpycPhY6cnUjvKra6wL+79ORj0WkT/4Z0CS
 SDmEO/Sl9SJlm0bVzg7Mq90Na3K7GEQiG7dFULEZD50uHG546xY+jazc/judWnqL
 fELrH/iwzuTB9ms5NkCvSh7B6I509LCJegwRu/Mxu0A6oHpfbuG/KUD0e2zIv1Qt
 3YwuC81l7zMjIuw9/QpRWrTBsNQ/2yMNXcHPxvifXOcivJFOk0qYHBGur3oRjJ+3
 KXaVMpSO9euxi8zY5fggU93j0oCO6QvrwyZz5F7DaUtTtgLgzmKpehKW9i2BZkRg
 MvsVd4s8LMcRxYI9IrwJsnjjGO7lVbFUsTcmnbyeQeJ0f4JqVUhGoN6BliXLGETK
 Gvk3aOIJyeG2+g86aEUu
 =KJzF
 -----END PGP SIGNATURE-----
 

Move build_and_test_android from ci.yml to pkgci.yml. (#18070)

Progress on https://github.com/iree-org/iree/issues/16203 and
https://github.com/iree-org/iree/issues/17957.

This migrates `.github/workflows/build_and_test_android.yml` to
`.github/workflows/pkgci_test_android.yml`.

**For now, this only builds for Android, it does not run tests or use
real Android devices at all**.

The previous workflow
* Relied on the "install" directory from a CMake build 
* Ran on large self-hosted CPU build machines
* Built within Docker (using
[`build_tools/docker/dockerfiles/android.Dockerfile`](https://github.com/iree-org/iree/blob/main/build_tools/docker/dockerfiles/android.Dockerfile))
* Used GCP/GCS for remote ccache storage
* Used GCP/GCS for passing files between jobs
* Ran tests on self-hosted lab machines (I think a raspberry pi
connected to some physical Android devices)

The new workflow
* Relies on Python packages produced by pkgci_build_packages
* Runs on standard GitHub-hosted runners
* Installs dependencies that it needs on-demand (ninja, Android NDK),
without using Docker
* Uses caches provided by GitHub Actions for ccache storage
* Could use Artifacts provided by GitHub Actions for passing files
between jobs
* Could run tests on self-hosted lab machines or Android emulators

I made some attempts at passing files from the build job to a test job
but ran into some GitHub Actions debugging that was tricky. Leaving the
remaining migration work there to contributors at Google or other
parties directly interested in Android CI infrastructure.

ci-exactly: build_packages, test_android