Skip to content

[AINFRA-435] Test Setup to Validate Android Agent (mac-metal) #14241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: trunk
Choose a base branch
from

Conversation

ParaskP7
Copy link
Contributor

@ParaskP7 ParaskP7 commented Jun 25, 2025

Related: #14153

Important

DO NOT MERGE — This PR is used to test CI scenarios only

This is a draft PR that I will use to (primary) run Android UI tests on the new CI agents (based on mac-metal), which is part of this project.

FYI: Currently this will be used to test AINFRA-433 but as the project progress I'm expecting I'll continue to use this dummy PR and branch to test more parts/steps/issues of the project (in the context of Android, mostly UI tests, as well as the generation of Baseline Profiles, see #12429).

@ParaskP7 ParaskP7 added status: do not merge Dependent on another PR, ready for review but not ready for merge. category: ui tests Related to UI testing. labels Jun 25, 2025
AliSoftware and others added 4 commits July 14, 2025 16:50
As expected this job is currently failing, see below:

:rubygems: Setting up Gems
Using a8c-ci-cache as cache bucket
No cache entry found for 'woocommerce-android-Darwin-arm64-libcmacos-
 15.3.2-ruby3.2.2-xyz'
Fetching bundler-2.5.20.gem
ERROR:  While executing gem ... (Gem::FilePermissionError)
    You don't have write permissions for the /Library/Ruby/Gems/2.6.0
     directory.
🚨 Error: The command exited with status 1
user command error: exit status 1

------------------------------------------------------------------------

Anyway, executing 'gradlew' and the 'connectedDebugAndroidTest'
directly, without setting up any Gems, or installing secrets should be
enough for now and this phase of testing.
@ParaskP7 ParaskP7 force-pushed the AINFRA-435/test-setup-to-validate-android-agent-mac-memtal branch from 7ebf42e to 9794627 Compare July 14, 2025 14:30
@AliSoftware
Copy link
Contributor

No big deal but FYI I already had #14153 as a dummy Draft PR to test WCAndroid builds on mac-metal 😛 😄

@ParaskP7
Copy link
Contributor Author

No big deal but FYI I already had #14153 as a dummy Draft PR to test WCAndroid builds on mac-metal 😛 😄

Of course, this is not news for me @AliSoftware and if you notice from the description itself (see Related on top), I based this on your #14153 PR, kept this one Test mac-metal queue job you had and then started adding more, Android specific jobs:

  1. Instrumented tests (ReviewsUITest) first, for AINFRA-435.
  2. Assemble then, for AINFRA-940.

FYI: I went with this approach in order to not pollute your PR, build logic with any Android specific jobs, and so that we could work on mac-metal testing in parallel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: ui tests Related to UI testing. status: do not merge Dependent on another PR, ready for review but not ready for merge.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants