Skip to content

Conversation

@flutter-pub-roller-bot
Copy link
Contributor

This PR was generated by flutter update-packages --force-upgrade.

@flutter-pub-roller-bot flutter-pub-roller-bot added tool Affects the "flutter" command-line tool. See also t: labels. autosubmit Merge PR when tree becomes green via auto submit App labels Nov 27, 2024
@github-actions github-actions bot added a: tests "flutter test", flutter_test, or one of our tests framework flutter/packages/flutter repository. See also f: labels. a: internationalization Supporting other languages or locales. (aka i18n) d: api docs Issues with https://api.flutter.dev/ d: examples Sample code and demos platform-web Web applications specifically f: integration_test The flutter/packages/integration_test plugin labels Nov 27, 2024
@auto-submit
Copy link
Contributor

auto-submit bot commented Nov 27, 2024

auto label is removed for flutter/flutter/159560, due to - The status or check suite Windows tool_integration_tests_7_9 has failed. Please fix the issues identified (or deflake) before re-applying this label.

@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Nov 27, 2024
@andrewkolos
Copy link
Contributor

Looks like something similar to #154507 will need to be done here.

From https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8729713836209442273/+/u/run_test.dart_for_tool_integration_tests_shard_and_subshard_5_5/stdout:

05:20 +34 -1: test/integration.shard/isolated/native_assets_test.dart: flutter run with native assets macos release [E]
  Expected: a process with exit code 0
    Actual: <Instance of 'ProcessResult'>
     Which: Actual exitCode was 1
            Actual stdout:
            Resolving dependencies...
            
            Actual stderr:
            Because test >=1.25.8 <1.25.9 depends on test_core 0.6.5 and every version of link_hook from path depends on test_core 0.6.6, test >=1.25.8 <1.25.9 is incompatible with link_hook from path.
            So, because package_with_native_assets depends on both link_hook from path and test 1.25.8, version solving failed.
            
            
            You can try the following suggestion to make the pubspec resolve:
            * Try upgrading your constraint on test: flutter pub add dev:test:^1.25.9
            Failed to update packages.
            
            
  
  package:matcher                                                      expect
  test/integration.shard/isolated/native_assets_test_utils.dart 57:3   createTestProject
  ===== asynchronous gap ===========================
  test/integration.shard/isolated/native_assets_test.dart 86:46        main.<fn>.<fn>
  ===== asynchronous gap ===========================
  test/integration.shard/isolated/native_assets_test_utils.dart 244:5  inTempDir
  ===== asynchronous gap ===========================
  test/integration.shard/isolated/native_assets_test.dart 85:9         main.<fn>

@dcharkes is it safe to bump all the dependencies in this template to the latest here?

@dcharkes
Copy link
Contributor

dcharkes commented Dec 2, 2024

@dcharkes is it safe to bump all the dependencies in this template to the latest here?

Yes, bumping dependencies should be safe.

(The error feels similar to 31c1292, the solution there was to unpin dependencies in the test I believe.)

@andrewkolos
Copy link
Contributor

@mkustermann May I ask you to take a look at this? It seems like you already have experience making these integration tests compatible with flutter update-packages.

@mkustermann
Copy link
Member

Normally I'd ask @dcharkes to make those tests robust against flutter updating pinned deps as he owns those tests.

Though since I handled one such issue before, I have taken a look now. I think we can handle it the same way I handled this before: #159715 may be sufficient to fix this.

@andrewkolos
Copy link
Contributor

From https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8729555030223274641/+/u/run_test.dart_for_flutter_plugins_shard_and_subshard_analyze/stdout:

Running command: "flutter pub downgrade" in /b/s/w/ir/x/t/flutter_packages.QAYQLR/packages/url_launcher/url_launcher_ios
Resolving dependencies...
Note: matcher is pinned to version 0.12.16+1 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.

Note: test_api is pinned to version 0.7.4 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.


Because test >=1.25.9 depends on analyzer >=6.0.0 <8.0.0 and test >=1.25.8 <1.25.9 depends on test_api 0.7.3, test >=1.25.8 requires analyzer >=6.0.0 <8.0.0 or test_api 0.7.3.
And because test >=1.25.6 <1.25.8 depends on test_api 0.7.2 and test >=1.25.3 <1.25.6 depends on test_api 0.7.1, test >=1.25.3 requires analyzer >=6.0.0 <8.0.0 or test_api 0.7.1 or 0.7.2 or 0.7.3.
And because test >=1.24.4 <1.25.0 depends on test_api 0.6.1 and test >=1.24.3 <1.24.4 depends on test_api 0.6.0, test >=1.24.3 <1.25.0-∞ or >=1.25.3 requires analyzer >=6.0.0 <8.0.0 or test_api 0.6.0 or 0.6.1 or 0.7.1 or 0.7.2 or 0.7.3.
And because test >=1.24.0 <1.24.3 depends on matcher >=0.12.15 <0.12.16 and test >=1.22.2 <1.24.0 depends on test_api 0.4.18, test >=1.22.2 <1.25.0-∞ or >=1.25.3 requires analyzer >=6.0.0 <8.0.0 or test_api 0.4.18 or 0.6.0 or 0.6.1 or 0.7.1 or 0.7.2 or 0.7.3 or matcher >=0.12.15 <0.12.16.
And because test >=1.22.1 <1.22.2 depends on test_api 0.4.17 and test >=1.22.0 <1.22.1 depends on test_api 0.4.16, test >=1.22.0 <1.25.0-∞ or >=1.25.3 requires analyzer >=6.0.0 <8.0.0 or test_api 0.4.16 or 0.4.17 or 0.4.18 or 0.6.0 or 0.6.1 or 0.7.1 or 0.7.2 or 0.7.3 or matcher >=0.12.15 <0.12.16.
And because test >=1.21.7 <1.22.0 depends on test_api 0.4.15 and test >=1.21.6 <1.21.7 depends on test_api 0.4.14, test >=1.21.6 <1.25.0-∞ or >=1.25.3 requires test_api 0.4.14 or 0.4.15 or 0.4.16 or 0.4.17 or 0.4.18 or 0.6.0 or 0.6.1 or 0.7.1 or 0.7.2 or 0.7.3 or analyzer >=6.0.0 <8.0.0 or matcher >=0.12.15 <0.12.16.
And because test >=1.25.0 <1.25.3 depends on test_api 0.7.0 and every version of flutter_test from sdk depends on matcher 0.12.16+1, if test >=1.21.6 and flutter_test from sdk then test_api 0.4.14 or 0.4.15 or 0.4.16 or 0.4.17 or 0.4.18 or 0.6.0 or 0.6.1 or 0.7.0 or 0.7.1 or 0.7.2 or 0.7.3 or analyzer >=6.0.0 <8.0.0.
And because pigeon >=10.0.1 <13.1.2 depends on analyzer ^5.13.0 and test >=1.16.6 <1.17.10 depends on analyzer ^1.0.0, if flutter_test from sdk and pigeon >=10.0.1 <13.1.2 and test >=1.16.6 <1.17.10-∞ or >=1.21.6 then test_api 0.4.14 or 0.4.15 or 0.4.16 or 0.4.17 or 0.4.18 or 0.6.0 or 0.6.1 or 0.7.0 or 0.7.1 or 0.7.2 or 0.7.3 or analyzer ^1.0.0.
And because test >=1.17.10 <1.20.0 depends on analyzer >=1.0.0 <3.0.0 and test >=1.21.0 <1.21.6 depends on analyzer >=2.0.0 <5.0.0, if flutter_test from sdk and pigeon >=10.0.1 <13.1.2 and test >=1.16.6 <1.20.0-∞ or >=1.21.0 then test_api 0.4.14 or 0.4.15 or 0.4.16 or 0.4.17 or 0.4.18 or 0.6.0 or 0.6.1 or 0.7.0 or 0.7.1 or 0.7.2 or 0.7.3 or analyzer >=1.0.0 <5.0.0.
And because mockito >=5.4.3 depends on analyzer >=5.12.0 <7.0.0 and test >=1.16.0-nullsafety.19 <1.16.6 depends on test_api 0.2.19, if mockito >=5.4.3 and flutter_test from sdk and pigeon >=10.0.1 <13.1.2 and test >=1.16.0-nullsafety.19 <1.20.0-∞ or >=1.21.0 then test_api 0.2.19 or 0.4.14 or 0.4.15 or 0.4.16 or 0.4.17 or 0.4.18 or 0.6.0 or 0.6.1 or 0.7.0 or 0.7.1 or 0.7.2 or 0.7.3.
And because test >=1.20.0 <1.21.2 depends on test_api 0.4.9 and every version of flutter_test from sdk depends on test_api 0.7.4, one of mockito >=5.4.3 or flutter_test from sdk or pigeon >=10.0.1 <13.1.2 or test >=1.16.0-nullsafety.19 must be false.
And because url_launcher_ios depends on both flutter_test from sdk and mockito ^5.4.4, pigeon >=10.0.1 <13.1.2 is incompatible with test >=1.16.0-nullsafety.19.
So, because url_launcher_ios depends on both pigeon ^11.0.1 and test ^1.16.3, version solving failed.

I don't see what is depending on test >=1.25.8 <1.25.9 👀. cc @bkonyi for any ideas.

@bkonyi
Copy link
Contributor

bkonyi commented Dec 3, 2024

I don't see what is depending on test >=1.25.8 <1.25.9 👀. cc @bkonyi for any ideas.

Ugh, I can never parse these version solving errors when they get like this... :(

Maybe @jakemac53 will have some insights since I think he has more experience with these sorts of conflicts.

@jakemac53
Copy link
Contributor

jakemac53 commented Dec 3, 2024

It looks like this is happening because of an old version of pigeon (latest is 22.6.3) - that version of pigeon doesn't support analyzer 6.x which is required by package:test >=1.25.9.

BTW, the secret to understanding these messages is to read the last line first :).

@jakemac53
Copy link
Contributor

(and it looks like url_launcher_ios is the thing with the outdated pigeon dep)

@bkonyi
Copy link
Contributor

bkonyi commented Dec 4, 2024

It looks like this is happening because of an old version of pigeon (latest is 22.6.3) - that version of pigeon doesn't support analyzer 6.x which is required by package:test >=1.25.9.

BTW, the secret to understanding these messages is to read the last line first :).

Thanks Jake! I typically do look at the last line but still have a hard time processing the message :(

@jakemac53
Copy link
Contributor

I wonder if a blog post or something just on how to understand these messages would be interesting 🤔 .

@jakemac53
Copy link
Contributor

I filed #159803 which is really the blocker here as far as I can tell, not sure who should take that on.

@stuartmorgan-g
Copy link
Contributor

url_launcher_ios 6.3.2 has been published with an updated pigeon dependency.

@christopherfujino
Copy link
Contributor

I'm gonna close this PR and let the bot open a new one.

However, I suspect it's gonna fail presubmits again because of an analyzer change, see: https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20analyze/89842/infra

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

a: internationalization Supporting other languages or locales. (aka i18n) a: tests "flutter test", flutter_test, or one of our tests d: api docs Issues with https://api.flutter.dev/ d: examples Sample code and demos f: integration_test The flutter/packages/integration_test plugin framework flutter/packages/flutter repository. See also f: labels. platform-web Web applications specifically tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants