Skip to content

Conversation

@micaelcid
Copy link
Contributor

@micaelcid micaelcid commented Aug 15, 2022

I just finished migrating a project to Android 13 that runs integration_test with Firebase Test Lab. In this PR, I am changing the exact dependencies I needed to change to make our application able to run integration tests targeting Android 13. (the project is currently depending on my fork).

Pre-launch Checklist

  • I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
  • I read the [Tree Hygiene] wiki page, which explains my responsibilities.
  • I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
  • I signed the [CLA].
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is [test-exempt].
  • All existing and new tests are passing.

@flutter-dashboard
Copy link

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@flutter-dashboard flutter-dashboard bot added the f: integration_test The flutter/packages/integration_test plugin label Aug 15, 2022
@google-cla
Copy link

google-cla bot commented Aug 15, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@flutter-dashboard
Copy link

This pull request executed golden file tests, but it has not been updated in a while (20+ days). Test results from Gold expire after as many days, so this pull request will need to be updated with a fresh commit in order to get results from Gold.

For more guidance, visit Writing a golden file test for package:flutter.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@jmagman jmagman added the framework flutter/packages/flutter repository. See also f: labels. label Feb 22, 2023
@goderbauer goderbauer added the platform-android Android applications specifically label Feb 28, 2023
@goderbauer
Copy link
Member

@reidbaker Can somebody from the Android team please check if this dependency bump makes sense? Thanks!

@reidbaker
Copy link
Contributor

Version bump is ok with me adding @ricardoamador in case updates cause us to have to add something our CI.
Not marking "Approved" on the cl until the integration tests pass and the build is up to date with master.

Copy link
Contributor

@ricardoamador ricardoamador left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@ricardoamador ricardoamador left a comment

Choose a reason for hiding this comment

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

Can you update the branch and make sure all tests are passing?

@micaelcid
Copy link
Contributor Author

Sure, @ricardoamador! I'll do as soon as I can. :) (Possibly today)

@micaelcid
Copy link
Contributor Author

@ricardoamador taking a glimpse at the failed tests, does it look like something you'd know the cause? Otherwise, is there any available documentation I could use to debug the CI problems myself?

@ricardoamador
Copy link
Contributor

ricardoamador commented Mar 2, 2023

@micaelcid If you look at the checks tab it will show you more details. Let me know if you are able to see the LUCI build information.
From taking a look at one of the windows tests it looks like there is a dependency failure:

Execution failed for task ':integration_test:generateDebugRFile'.
 [        ] > Could not resolve all files for configuration ':integration_test:debugCompileClasspath'.
 [        ]    > Did not resolve 'net.sf.kxml:kxml2:2.3.0' which is part of the dependency lock state
 [        ]    > Resolved 'androidx.test.services:storage:1.4.0' which is not part of the dependency lock state
 [        ]    > Could not resolve androidx.test:runner:1.4.0.
 [        ]      Required by:
 [        ]          project :integration_test
 [        ]          project :integration_test > androidx.test:rules:1.4.0
 [        ]          project :integration_test > androidx.test.espresso:espresso-core:3.4.0
 [        ]       > Cannot find a version of 'androidx.test:runner' that satisfies the version constraints:
 [        ]            Dependency path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test:runner:1.4.0'
 [        ]            Constraint path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test:runner:{strictly 1.2.0}' because of the following reason: dependency was locked to version '1.2.0'
 [        ]            Dependency path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test:rules:1.4.0' --> 'androidx.test:runner:1.4.0'
 [        ]            Dependency path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test.espresso:espresso-core:3.4.0' --> 'androidx.test:runner:1.4.0'
 [        ]    > Could not resolve androidx.test:rules:1.4.0.
 [        ]      Required by:
 [        ]          project :integration_test
 [        ]       > Cannot find a version of 'androidx.test:rules' that satisfies the version constraints:
 [        ]            Dependency path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test:rules:1.4.0'
 [        ]            Constraint path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test:rules:{strictly 1.2.0}' because of the following reason: dependency was locked to version '1.2.0'
 [        ]    > Could not resolve androidx.test.espresso:espresso-core:3.4.0.
 [        ]      Required by:
 [        ]          project :integration_test
 [        ]       > Cannot find a version of 'androidx.test.espresso:espresso-core' that satisfies the version constraints:
 [        ]            Dependency path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test.espresso:espresso-core:3.4.0'
 [        ]            Constraint path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test.espresso:espresso-core:{strictly 3.2.0}' because of the following reason: dependency was locked to version '3.2.0'
 [        ]    > Could not resolve androidx.test.espresso:espresso-core:{strictly 3.2.0}.
 [        ]      Required by:
 [        ]          project :integration_test
 [        ]       > Cannot find a version of 'androidx.test.espresso:espresso-core' that satisfies the version constraints:
 [        ]            Dependency path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test.espresso:espresso-core:3.4.0'
 [        ]            Constraint path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test.espresso:espresso-core:{strictly 3.2.0}' because of the following reason: dependency was locked to version '3.2.0'
 [        ]    > Could not resolve androidx.test:runner:{strictly 1.2.0}.
 [        ]      Required by:
 [        ]          project :integration_test
 [        ]       > Cannot find a version of 'androidx.test:runner' that satisfies the version constraints:
 [        ]            Dependency path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test:runner:1.4.0'
 [        ]            Constraint path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test:runner:{strictly 1.2.0}' because of the following reason: dependency was locked to version '1.2.0'
 [        ]            Dependency path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test:rules:1.4.0' --> 'androidx.test:runner:1.4.0'
 [        ]            Dependency path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test.espresso:espresso-core:3.4.0' --> 'androidx.test:runner:1.4.0'
 [        ]    > Could not resolve androidx.test:rules:{strictly 1.2.0}.
 [        ]      Required by:
 [        ]          project :integration_test
 [        ]       > Cannot find a version of 'androidx.test:rules' that satisfies the version constraints:
 [        ]            Dependency path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test:rules:1.4.0'
 [        ]            Constraint path 'com.example.integration_test:integration_test:1.0-SNAPSHOT' --> 'androidx.test:rules:{strictly 1.2.0}' because of the following reason: dependency was locked to version '1.2.0'
 [        ] * Try:

Are you able to see this link?
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8787738512540060369/+/u/run_test.dart_for_build_tests_shard_and_subshard_1_3/test_stdout

@micaelcid
Copy link
Contributor Author

micaelcid commented Mar 2, 2023

Thanks! I can @ricardoamador, except for Linux firebase_release_smoke_test step that returns only a one-line message:
image

@ricardoamador
Copy link
Contributor

Ah okay. You need to follow the link at the botton of that screen. The one that says 'View more details on flutter-dashboard.' I know it kind of small and can easily be missed. That error is the same though. You can see it here:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8787738512559017217/+/u/test_execution/Build_appbundle/stdout

@micaelcid
Copy link
Contributor Author

Thanks again, I'm totally newbie to open sourcing, but I'll work my way around :)

@ricardoamador
Copy link
Contributor

Sure no problem!

@micaelcid micaelcid force-pushed the master branch 3 times, most recently from 03b241c to fdab7d8 Compare March 5, 2023 15:30
@reidbaker reidbaker added the autosubmit Merge PR when tree becomes green via auto submit App label Mar 6, 2023
@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Mar 6, 2023
@auto-submit
Copy link
Contributor

auto-submit bot commented Mar 6, 2023

auto label is removed for flutter/flutter, pr: 109547, due to - The status or check suite Mac module_host_with_custom_build_test has failed. Please fix the issues identified (or deflake) before re-applying this label.

@micaelcid
Copy link
Contributor Author

Hey, @reidbaker. Thanks for adding the label. It seems the pipeline step failed due to some flakiness. Could you try again, please?

@reidbaker reidbaker added the autosubmit Merge PR when tree becomes green via auto submit App label Mar 7, 2023
@auto-submit auto-submit bot merged commit 41fbf46 into flutter:master Mar 7, 2023
zanderso added a commit that referenced this pull request Mar 7, 2023
auto-submit bot pushed a commit that referenced this pull request Mar 7, 2023
…122106)

Revert "[integration_test] upgrade androidx test to 1.4.0"
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2023
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2023
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2023
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request May 10, 2023
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autosubmit Merge PR when tree becomes green via auto submit App c: contributor-productivity Team-specific productivity, code health, technical debt. f: integration_test The flutter/packages/integration_test plugin framework flutter/packages/flutter repository. See also f: labels. platform-android Android applications specifically

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants