-
Notifications
You must be signed in to change notification settings - Fork 219
Failed assertions when #2498
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
Comments
@DanTup can you take a look? |
Yep, looking... I guess these asserts are the ones to ensure we had consistent parents when cloning the groups/tests. |
@bkonyi btw, it looks like this is already pinned in Flutter? Did the attempted roll change this to get the broken version, or is something else up too? Edit: nm, I found your PR flutter/flutter#168916 that updated this - I'll debug using that PR! |
@bkonyi I don't suppose you can repro this locally? I'm struggling with your PR (with the fix taken out) either running the Flutter tests, or the sample test directly. I believe I know what the issue is - I think we're missing clones of setUpAll/tearDownAll here: I'm working on a fix, but it'd be good to verify it solves the problem here by being able to repro the issue without having to release etc. Edit: nm, |
When groups are filtered using `filter()` and not `onPlatform`, we would clone the group and tests without also cloning `setUpAll`/`tearDownAll`, which led to an assertion failure when trying to set the parents. This change ensures we clone tests in `filter()` like we do in `forPlatform()`. Fixes dart-lang#2498
I was able to repro locally with Flutter by setting |
When groups are filtered using `filter()` and not `onPlatform`, we would clone the group and tests without also cloning `setUpAll`/`tearDownAll`, which led to an assertion failure when trying to set the parents. This change ensures we clone tests in `filter()` like we do in `forPlatform()`. Fixes #2498
These packages were recently pinned (in flutter#168916) due to a bug (dart-lang/test#2498). That bug was fixed and new versions of the test packages published. This change unpins and lets them upgrade to the fixed version.
I missed that @jakemac53 had already published these fixes, so anyone with failures should see them fixed now (or if had pinned to the previous version, can unpin). @bkonyi I've started on a PR to unpin the packages in Flutter to verify everything passes this time (flutter/flutter#169198). |
These packages were recently pinned (in #168916) due to a bug (dart-lang/test#2498). That bug was fixed and new versions of the test packages published. This change unpins and lets them upgrade to the fixed version.
When attempting to do a pub package roll into the Flutter framework, we've started encountering failures due to assertions added in 935b8b0.
In particular, we're seeing this assertion fail in all three tests referencing
flutter/dev/automated_tests/flutter_test/trivial_widget_test.dart
influtter/packages/flutter_tools/test/integration.shard/test_test.dart
:Full logs are here.
I'm going to pin the dependency on
package:test_api
to0.7.4
prevent the latest change from being pulled in.FYI @DanTup @jakemac53
The text was updated successfully, but these errors were encountered: