Skip to content

unit tests: limiting maximum memory usage #248

Open
@anholt

Description

@anholt

In order to complete the unit tests in a reasonable amount of time on low-end boards, I'd like to parallelize them. However, this runs into OOMkiller trouble with the larger resolutions being tested. My questions I have so far:

  • I'm seeing 8k and 10k being allocated with 10 surfaces from CreateSurfaces -- is 10 a reasonable number of surfaces to need for all entrypoints?
  • Could we clamp surface creation to getMinMaxSurfaceResolution()?
  • Could we bake resolution name into test names so I can either filter out the large resolutions, or test them single-threaded?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions