[flame_3d] Fix unrelated broken tests on main due to bug on drawRawAtlas

Open
#3,301 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
dart, flutter
Domain
game-dev, testing

Research direction

Start with the tests flagged on PR #3299 and inspect the drawRawAtlas bug they expose on Flutter main. Reproduce the failure on the affected test suite, then confirm the relevant tests pass without breaking the Flame 3D changes.

Written by the indexing model from the issue text.

Description

bug
What happened?

The tests flagged on this PR do not work on Flutter main.
That has nothing to do with Flame 3D but it is breaking our build.

What do you expect?

Tests to pass.

How can we reproduce this?

No response

What steps should take to fix this?

No response

Do have an example of where the bug occurs?

No response

Relevant log output

No response

Execute in a terminal and put output into the code block below

Output of: flutter doctor -v

Affected platforms

All

Other information

No response

Are you interested in working on a PR for this?
  • I want to work on this
Dominant language
Dart
Stars
10.8k
Forks
1.1k
Avg merge
2d 4h
Merged PRs (30d)
61

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flame-engine/flame

All issues in flame-engine/flame

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.