[AINFRA-435] Test Setup to Validate Android Agent (mac-metal)
#14241
+131
−100
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ParaskP7
added
status: do not merge
ParaskP7
force-pushed
the
AINFRA-435/test-setup-to-validate-android-agent-mac-memtal
branch
from
7ebf42e to
9794627
Compare
|
No big deal but FYI I already had #14153 as a dummy Draft PR to test WCAndroid builds on |
Of course, this is not news for me @AliSoftware and if you notice from the description itself (see
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 |
ParaskP7
force-pushed
the
AINFRA-435/test-setup-to-validate-android-agent-mac-memtal
branch
from
ba37e6d to
3e78cdc
Compare
ParaskP7
force-pushed
the
AINFRA-435/test-setup-to-validate-android-agent-mac-memtal
branch
7 times, most recently
from
f2c9477 to
9a20ca0
Compare
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
force-pushed
the
AINFRA-435/test-setup-to-validate-android-agent-mac-memtal
branch
from
c9b7937 to
2bad365
Compare
ParaskP7
force-pushed
the
AINFRA-435/test-setup-to-validate-android-agent-mac-memtal
branch
from
2bad365 to
91fabe1
Compare
To avoid encountering issues when a previous CI job on the same mac-metal machine already installed a previous APK
…ook we have on mac-metal will properly take care of the safety cleanup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).