-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
bugSomething isn't workingSomething isn't workingwontfixThis will not be worked onThis will not be worked on
Description
Description
We need to enhance our CI/CD pipelines (Azure CI) to include automated test and benchmark execution. Currently, there's a blocking issue preventing proper test execution on Windows systems.
Problem
When attempting to run tests in the CI environment, we encounter a 0xc135 error code (STATUS_DLL_NOT_FOUND), indicating that required DLLs cannot be located during test execution. The root cause of this DLL resolution issue is currently unclear.
Requirements
- Configure Azure CI pipeline to execute tests and benchmarks
- Resolve the Windows DLL loading issue (error code 0xc135)
- Ensure all dependencies are properly available during CI execution
Current Status
- CI pipelines exist but don't run tests/benchmarks
- Tests fail with
0xc135(NOT_FOUND_DLL) error on Windows - Local test execution may work fine, issue appears CI-specific
Acceptance Criteria
- Azure CI successfully runs all tests
- Azure CI successfully runs benchmarks
- Windows DLL loading issue is resolved
- CI fails appropriately when tests fail
- Test results are properly reported in CI interface
Additional Context
The error code 0xc135 (STATUS_DLL_NOT_FOUND) suggests missing dependencies in the CI environment. This could be related to (maybe):
- Missing Visual C++ redistributables
- Incorrect PATH configuration
- Missing system libraries
- Architecture mismatch (x86 vs x64)
Investigation needed to determine exact cause and implement appropriate fix.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingwontfixThis will not be worked onThis will not be worked on