Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate ways to make memory_trap_1_check_throw run within CICD time limits #232

Open
linh2931 opened this issue Jun 4, 2024 · 1 comment

Comments

@linh2931
Copy link
Member

linh2931 commented Jun 4, 2024

memory_trap_1_check_throw consistently run over the CICD time limit (8 minutes). To get code submission to main going, it was split into 2 tests by 4fa0af1 in #205. But future regeneration of the WASM spect test will restore it back to a single test.

Need to either increase the time need or modify the generator in a future task.

@bhazzard
Copy link

This is working for now, so not a priority at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

3 participants