-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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
[macos] native_assets_test.dart: flutter run hot reload and hot restart with native assets macos debug is flaky #148955
Comments
cc @dcharkes |
I have run the test multiple times locally, but I am also unable to reproduce this. If it's flaky, the Flutter CI should not notice and file a P0 issue and assign it to me (I'm the test owner). |
I opened this in case you have any idea what this could be caused by. It looks like a potential issue with duplicate framework name prevention (package_with_native_assets1.framework), but in macos/debug there's only one architecture so I don't quite see the codepath that could be causing this. |
@dcharkes this is happening in Line 334 in c77c0cf
It's failed four times in the last three commits: |
I can't reproduce this locally, but inspecting the temp folder unit test yields: format-version:
- 1
- 0
- 0
native-assets:
macos_arm64:
package:package_with_native_assets/package_with_native_assets_bindings_generated.dart:
- absolute
- package_with_native_assets.framework/package_with_native_assets
package:link_hook/link_hook_bindings_generated.dart:
- absolute
- link_hook.framework/link_hook
macos_x64:
package:package_with_native_assets/package_with_native_assets_bindings_generated.dart:
- absolute
- package_with_native_assets1.framework/package_with_native_assets1
package:link_hook/link_hook_bindings_generated.dart:
- absolute
- link_hook1.framework/link_hook1 I'm thinking that somehow the order of architectures gets switched during hot reload or hot restart on the bot, causing the two different names to swap archs. Now, these shouldn't be different names to begin with. This was recently fixed in iOS (02d5286), but not in MacOS. I've created #149761 to address this. |
This issue is assigned to @dcharkes but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks! |
I believe the mentioned commit fixed it, the bot is no longer red: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20tool_integration_tests_4_4 |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Integration test sometimes fails with
I'm unable to reproduce this locally.
The text was updated successfully, but these errors were encountered: