https://wiki.nesdev.com/w/index.php/Emulator_tests

It could run these ROMs and actually check the output somehow - perhaps either by checking memory values, or a copy of the screen buffer.

People seem to use Vulkan despite the d3d12 backend being superior, so add a message so people stop asking which backend is better.

Currently allocation a virtual region of GPU memory does a linear search over all the pages, to find a region of free pages of the requested size. Relevant code: https://github.com/Ryujinx/Ryujinx/blob/b8eb6abeccbd4a468214a4d2ad3a9b6e5e06973c/Ryujinx.Graphics.Gpu/Memory/MemoryManager.cs#L201

This may have a negative performance impact on games that does a lot of such allocations (example: creat

It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the

@Johnnynator says that it will boost build speed