test: Exclude flame_3d from the flutter/tests customer_testing run#3942
Merged
Conversation
flame_3d builds on the experimental flutter_gpu library, whose API changes frequently in flutter/flutter's presubmit. Analyzing it there blocks framework changes on an unstable dependency that is not representative of Flame, so it is excluded from the customer_testing run while every other package is still analyzed and tested.
wolfenrain
approved these changes
Jul 3, 2026
spydon
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Follow-up to #3941.
flame_3dbuilds on the experimentalflutter_gpulibrary, whose API changes frequently in flutter/flutter's presubmit. Because the customer_testing script runsflutter analyzeover the whole workspace, those upstream changes break the analyze step and would block flutter/flutter framework PRs on an unstable dependency that is not representative of Flame.This excludes
flame_3dfrom the customer_testing run (both analyze and tests) while every other package is still analyzed and tested. Analyze now targetsdocplus each package directory exceptflame_3d, preserving the previous coverage.flame_3dstill compiles and tests cleanly against the stable Flutter that Flame targets; it simply cannot track the experimental engine API on flutter/flutter master.Checklist
melos formatandmelos analyze(or an equivalent) and it passes.