Skip to content
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

CI Workflow Dependency Upgrades + Optimization 👷 #3369

Merged
merged 15 commits into from
Jul 24, 2024
Merged

Conversation

ndegwamartin
Copy link
Contributor

@ndegwamartin ndegwamartin commented Jul 4, 2024

IMPORTANT: Where possible all PRs must be linked to a Github issue

Resolves #3407

Engineer Checklist

  • I have written Unit tests for any new feature(s) and edge cases for bug fixes
  • I have added any strings visible on UI components to the strings.xml file
  • I have updated the CHANGELOG.md file for any notable changes to the codebase
  • I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
  • I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app
  • I have checked that this PR does NOT introduce breaking changes that require an update to Content and/or Configs? If it does add a sample here or a link to exactly what changes need to be made to the content.

Code Reviewer Checklist

  • I have verified Unit tests have been written for any new feature(s) and edge cases
  • I have verified any strings visible on UI components are in the strings.xml file
  • I have verifed the CHANGELOG.md file has any notable changes to the codebase
  • I have verified the solution has been implemented in a configurable and generic way for reuseable components
  • I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

Copy link

codecov bot commented Jul 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 28.1%. Comparing base (c67c1dc) to head (f756ca7).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff            @@
##              main   #3369     +/-   ##
=========================================
- Coverage     28.2%   28.1%   -0.1%     
  Complexity     718     718             
=========================================
  Files          265     265             
  Lines        12871   12881     +10     
  Branches      2313    2315      +2     
=========================================
  Hits          3630    3630             
- Misses        8765    8774      +9     
- Partials       476     477      +1     
Flag Coverage Δ
engine 64.9% <ø> (ø)
geowidget 12.8% <ø> (ø)
quest 4.7% <ø> (-0.1%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

@ndegwamartin ndegwamartin force-pushed the ci-opti-upgrade branch 3 times, most recently from fc4baea to 5b5d1c2 Compare July 9, 2024 18:05
pld
pld previously approved these changes Jul 9, 2024
@pld
Copy link
Member

pld commented Jul 10, 2024

this is the main error I see in the quest logs

2024-07-10T18:55:27.7610798Z Error: Failed to generate Emma/JaCoCo coverage. Is Emma/JaCoCo jar on classpath?

@@ -17,7 +18,7 @@ env:

jobs:
engine-tests:
runs-on: macos-13
runs-on: ubuntu-latest
Copy link
Collaborator

Choose a reason for hiding this comment

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

Does the Ubuntu image include an emulator? The macOS image was used to allow us to run instrumentation tests.

Copy link
Collaborator

Choose a reason for hiding this comment

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

The performance tests require an emulator to run.

Copy link
Member

@pld pld Jul 18, 2024

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah and its actually much faster. Preliminary tests show around 50% improvement for the jobs

@ndegwamartin
Copy link
Contributor Author

this is the main error I see in the quest logs

2024-07-10T18:55:27.7610798Z Error: Failed to generate Emma/JaCoCo coverage. Is Emma/JaCoCo jar on classpath?

This is caused by disabling the instrumentation tests in the gradle configuration file. When disabled the reporting artifacts are not loaded. Note, we can only enable it after resolving #3055

* Upgrade JUnit 5
* Update CI configuration for maintainability 👷
* Refactor Gradle Configs for maintainability 🔧
* Refactor unit tests to runTest
@ndegwamartin ndegwamartin enabled auto-merge July 23, 2024 15:45
@ndegwamartin ndegwamartin added this pull request to the merge queue Jul 24, 2024
Merged via the queue into main with commit 9b51114 Jul 24, 2024
5 checks passed
@ndegwamartin ndegwamartin deleted the ci-opti-upgrade branch July 24, 2024 15:47
qiarie pushed a commit that referenced this pull request Jan 15, 2025
* CI Workflow Dependency Upgrades + Optimization 👷

* Migrate CI workflow to use Ubuntu runner

* Update CI Workflow with KVM

* Troubleshooting: Force recreation of AVD for Quest

* Troubleshooting: Update CI Workflow configuration

* Update Quest module workflow configuration | AVD

* Troubleshooting configuration
- Add workflow dispatch event trigger
- Disable CI runs for working modules
- Reset Quest test run and reporting configuration

* Update CI workflow configuration
- Update path to emulator SDK
- Enable Engine and Geowidget jobs

* Update CI workflow configuration:Quest Tests 👷

* Add Target SDK build.gradle configuration 🔧

* Unit Test troubleshooting

* Unit Test troubleshooting

* Troubleshooting: Quest module Unit Tests

* Apply Spotless to Quest

* [DNM] Quest Module tests troubleshooting (#3387)

* Upgrade JUnit 5
* Update CI configuration for maintainability 👷
* Refactor Gradle Configs for maintainability 🔧
* Refactor unit tests to runTest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add targetSdk to modules
3 participants