Separate code size tests to its own dedicated suite?

[juj]

Something that came to mind when staring failures like this:

It might be a good idea to separate all code size tests to its own suite test_codesize.py and run in codesize.test_xxx namespace.

Then for CircleCI maybe the code size tests could be run in a task of its own. That way one would be able to see at a glance if it is a code size rebaselining problem that caused the code size regression?

[sbc100]

Good idea. I thing @brendandahl suggested this too.

We could start by adding EMTEST_SKIP_CODESIZE which we could enable on all the builders except the code size one. That could then also be used by the emscripten-releases builder which currently hardcode some patterns: https://chromium.googlesource.com/emscripten-releases/+/refs/heads/main/bots.json#136:

--test-param=other,skip:other.*_codesize*,skip:other.*_code_size*,skip:other.test_cmake_find_pkg_config

Or we could just move them..either approach sounds reasonable to me.