-
Notifications
You must be signed in to change notification settings - Fork 724
[UNIT] enhance complication unit test case #4641
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
base: dev/ai_generated_cases
Are you sure you want to change the base?
[UNIT] enhance complication unit test case #4641
Conversation
pugong2019
commented
Sep 22, 2025
- Advanced compiler configurations and feature combinations - Memory optimization and profiling settings - Platform-specific compilation options - Resource management and lifecycle testing - Optimization level validation across all supported levels Signed-off-by: Gong Pu <[email protected]>
…ompilation module - Add SIMD WAT test module with 25+ vector operations covering: * Lane access (extract/replace), bitmask operations * Bitwise operations (and, or, xor, not) * Boolean reductions (any_true, all_true) * Comparisons, conversions, and arithmetic * Load/store operations and saturated arithmetic - Create test_simd_advanced_instructions.cc with proper RAII resource management Signed-off-by: Gong Pu <[email protected]>
… testing improvement: - Add test_llvm_integration_optimization.cc with LLVM backend validation - Test optimization passes, code generation, and target machine setup - Cover PGO, vectorization, register allocation, and cross-compilation - Add llvm_test.wat/wasm for LLVM-specific compilation testing - Add test_integration_performance.cc for end-to-end workflow validation - Implement performance benchmarking and memory profiling tests - Add concurrent compilation, stress testing, and error recovery - Test multi-module compilation and deterministic output validation Signed-off-by: Gong Pu <[email protected]>
…ion_feature_test_plan.md Detailed Implementation Records: - Added commit references for each step - Updated test case counts (80 total test cases) - Added quality scores and coverage impact details - Documented implementation files and WAT resources Signed-off-by: Gong Pu <[email protected]>
…ts to resolve 22 test failures - Add proper WAMR runtime initialization in IntegrationPerformanceTest::SetUp() - Replace FAIL() with ASSERT_TRUE() for better test practices - Add proper cleanup in TearDown() with wasm_runtime_destroy() - Fix all 20 IntegrationPerformanceTest cases (tests 423-442) - Fix LLVMIntegrationOptimizationTest.test_llvm_target_machine_setup - Fix SIMDAdvancedInstructionsTest.test_aot_emit_exception_handling_compilation Root cause: Tests were attempting to use WAMR functions before runtime initialization, causing "wasm_runtime_malloc failed: memory hasn't been initialized" errors. Signed-off-by: Gong Pu <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WIP. not finished.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually, we don't commit binaries, like .wasm files. They should be generated from .wat files (which you have) during compilation before executing test cases.
tests/unit/enhanced_unit_test/ ==> tests/unit/enhanced-unit-test/ |