Skip to content

ci: setup Java and adb in runner health check (WPB-21881)#4568

Merged
MohamadJaara merged 13 commits intodevelopfrom
ci/WPB-21881-runner-health-check-fix
Feb 9, 2026
Merged

ci: setup Java and adb in runner health check (WPB-21881)#4568
MohamadJaara merged 13 commits intodevelopfrom
ci/WPB-21881-runner-health-check-fix

Conversation

@emmaoke-w
Copy link
Contributor

@emmaoke-w emmaoke-w commented Feb 5, 2026

https://wearezeta.atlassian.net/browse/WPB-21881


PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

  • Adds a manual GitHub Actions workflow to verify QA Android runner health.
  • Ensures the runner can execute jobs, has Java and ADB available, and can detect authorized Android devices.
  • Helps quickly diagnose runner/device issues before running Android UI tests.

Issues

Briefly describe the issue you have solved or implemented with this pull request. If the PR contains multiple issues, use a bullet list.

Causes (Optional)

Briefly describe the causes behind the issues. This could be helpful to understand the adopted solutions behind some nasty bugs or complex issues.

Solutions

Briefly describe the solutions you have implemented for the issues explained above.

Dependencies (Optional)

If there are some other pull requests related to this one (e.g. new releases of frameworks), specify them here.

Needs releases with:

  • GitHub link to other pull request

Testing

Test Coverage (Optional)

  • I have added automated test to this contribution

How to Test

Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.

Notes (Optional)

Specify here any other facts that you think are important for this issue.

Attachments (Optional)

Attachments like images, videos, etc. (drag and drop in the text box)


PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

Comment on lines 45 to 46
# Add adb to PATH for the rest of this workflow
echo "$HOME/platform-tools/platform-tools" >> "$GITHUB_PATH"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i am not sure about this working for the rest of the workflow i would exoect it to look like

          export PATH="$HOME/platform-tools/platform-tools:$PATH"

but not 100% sure about it

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or you can just leave it as it is and check the adb version in th next step

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

@emmaoke-w looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop This PR
0ac7c385b7dbbf9334125ff4eae9636d212134ad ae71a9a75ae63027c8970905ef5bdeabc59fee8b

Is this intentional?

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

@emmaoke-w looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop This PR
0ac7c385b7dbbf9334125ff4eae9636d212134ad ae71a9a75ae63027c8970905ef5bdeabc59fee8b

Is this intentional?

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

@emmaoke-w looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop This PR
0ac7c385b7dbbf9334125ff4eae9636d212134ad ae71a9a75ae63027c8970905ef5bdeabc59fee8b

Is this intentional?

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

@emmaoke-w looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop This PR
0ac7c385b7dbbf9334125ff4eae9636d212134ad ae71a9a75ae63027c8970905ef5bdeabc59fee8b

Is this intentional?

@emmaoke-w emmaoke-w removed the request for review from jschumacher-wire February 9, 2026 09:37
@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

@emmaoke-w looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop This PR
0ac7c385b7dbbf9334125ff4eae9636d212134ad ae71a9a75ae63027c8970905ef5bdeabc59fee8b

Is this intentional?

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

@emmaoke-w looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop This PR
0ac7c385b7dbbf9334125ff4eae9636d212134ad ae71a9a75ae63027c8970905ef5bdeabc59fee8b

Is this intentional?

Copy link
Member

@MohamadJaara MohamadJaara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@codecov
Copy link

codecov bot commented Feb 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 48.60%. Comparing base (7ceee93) to head (01763ea).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #4568   +/-   ##
========================================
  Coverage    48.60%   48.60%           
========================================
  Files          576      576           
  Lines        19931    19931           
  Branches      3339     3339           
========================================
  Hits          9688     9688           
  Misses        9214     9214           
  Partials      1029     1029           

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ceee93...01763ea. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 9, 2026

Copy link
Collaborator

@CinnamonNinja CinnamonNinja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@MohamadJaara MohamadJaara added this pull request to the merge queue Feb 9, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 9, 2026
@MohamadJaara MohamadJaara added this pull request to the merge queue Feb 9, 2026
Merged via the queue into develop with commit 4f0dc9c Feb 9, 2026
22 checks passed
@MohamadJaara MohamadJaara deleted the ci/WPB-21881-runner-health-check-fix branch February 9, 2026 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants