Skip to content

Remove test_emcc_4. NFC#26440

Merged
sbc100 merged 1 commit intoemscripten-core:mainfrom
sbc100:remove_test
Mar 12, 2026
Merged

Remove test_emcc_4. NFC#26440
sbc100 merged 1 commit intoemscripten-core:mainfrom
sbc100:remove_test

Conversation

@sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Mar 12, 2026

This is a rather sprawling and unfocused test that has a huge loop inside.

This single test take over 30 seconds to run.

It seems to test for a lot of different things, including stuff from the old compile-to-JS days. I'm pretty sure all this stuff is covered in a more logical fashion elsewhere.

It also has a very useless name.

@sbc100 sbc100 requested a review from kripken March 12, 2026 00:26
if opt_level == 0 or '-g' in params:
assert looks_unminified
elif opt_level >= 2:
assert looks_minified
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One thing I'm not sure if other tests cover is closure (that closure runs exactly when asked). Code size tests might indirectly, but I think those run without closure so that we can see function names?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The codesize tests absolutes do use closure. We sometimes build twice to get names I think but the core measurements are all about closure.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm.. I just noticed that closure is always 0 here... i.e. we are not actually ever testing if closure ran

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like even more evidence that this test is bittrotted/not doing much anymore.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

This is a rather sprawling and unfocused test that has a huge loop
inside.

This single test take over 30 seconds to run.

It seems to test for a lot of different things, including stuff from
the old compile-to-JS days.  I'm pretty sure all this stuff is covered
in a more logical fashion elsewhere.

It also has a very useless name.
@sbc100 sbc100 enabled auto-merge (squash) March 12, 2026 20:11
@sbc100 sbc100 requested a review from kripken March 12, 2026 20:11
if opt_level == 0 or '-g' in params:
assert looks_unminified
elif opt_level >= 2:
assert looks_minified
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

@sbc100 sbc100 disabled auto-merge March 12, 2026 21:12
@sbc100 sbc100 merged commit 5f044a5 into emscripten-core:main Mar 12, 2026
33 of 37 checks passed
@sbc100 sbc100 deleted the remove_test branch March 12, 2026 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants