Skip to content

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Aug 29, 2025

This allows us remove some the nested loops from these tests.

Ideally all_engines would generate separate tests for each engine but that can be a followup change.

@sbc100 sbc100 changed the title Use all_engines more consistently [test] Use all_engines more consistently. NFC Aug 29, 2025
@sbc100 sbc100 requested a review from kripken August 29, 2025 22:41

for engine in config.JS_ENGINES:
if engine == config.V8_ENGINE:
print('skipping v8 due to https://github.com/emscripten-core/emscripten/issues/25010')
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 is has been fixed.

@sbc100 sbc100 force-pushed the js_engines branch 4 times, most recently from 2b5f0b7 to e167568 Compare August 29, 2025 23:25
This allows us remove some the nested loops from these tests.

Ideally `all_engines` would generate separate tests for each engine but
that can be a followup change.
@sbc100
Copy link
Collaborator Author

sbc100 commented Aug 30, 2025

I have a great followup that actually splits these into one-test-per-engine

@sbc100
Copy link
Collaborator Author

sbc100 commented Aug 30, 2025

Here is my followup which I'm pretty happy with: #25115

@sbc100 sbc100 merged commit 96371ed into emscripten-core:main Sep 2, 2025
30 checks passed
@sbc100 sbc100 deleted the js_engines branch September 2, 2025 16:04
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