Disable Android e2e tests while we investigate foundational breakage

[dcalhoun]

Description

A adb: no devices/emulators found error is occurring and cause every run to fail. We intend to temporarily disable this job while we investigate the cause to avoid causing disruptions or confusion for contributors.

How has this been tested?

Verify all CI checks succeed.

Screenshots

n/a

Types of changes

Tooling change.

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR (please manually search all *.native.js files for terms that need renaming or removal).

[fluiddot]

I see in the PR checks that the Android e2e tests job is still failing, shouldn't have disappeared with the changes?

[dcalhoun]

I see in the PR checks that the Android e2e tests job is still failing, shouldn't have disappeared with the changes?

Yes, that was my intention. However, it looks like an empty branches: [] configuration includes every branch, including this one, as indicated in the latest CI task run. I'll see if I can identify a better fix.

[fluiddot]

I see in the PR checks that the Android e2e tests job is still failing, shouldn't have disappeared with the changes?

Yes, that was my intention. However, it looks like an empty branches: [] configuration includes every branch, including this one, as indicated in the latest CI task run. I'll see if I can identify a better fix.

I think you could disable it by adding this to the workflow (solution reference):
if: false # always skip job

[mchowning]

Changes look good., so if CI is happy, then I am happy. 😄