You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Improve JET tests to cover all solvers
This commit significantly expands the JET test coverage for LinearSolve.jl to test every available solver type. The improvements include:
- **Complete solver coverage**: Added JET tests for all dense factorizations, sparse factorizations, Krylov methods, and extension-based solvers
- **Proper test organization**: Organized tests into logical groups with clear testsets for better readability and maintenance
- **Appropriate test problems**: Created specific test problems (symmetric, SPD, sparse) for solvers that require them
- **Graceful failure handling**: Used @test_skip for tests that currently fail JET optimization checks, making them visible without blocking CI
- **Platform-specific handling**: Added conditional checks for platform-specific solvers (MKL, Apple Accelerate)
The tests now provide comprehensive coverage while properly handling expected failures, making it easier to track and improve type stability across the codebase.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
* Fix JET tests to avoid test failures on CI
The previous approach using @test_skip didn't work correctly because JET.@test_opt doesn't return a Boolean value when it fails. Instead, it throws a test failure which cannot be caught with @test_skip.
This commit simplifies the test file by:
- Only running JET tests that currently pass
- Documenting all failing tests with TODO comments explaining the type stability issues
- Providing the full test suite as commented code for future fixes
This ensures CI passes while still providing visibility into which solvers need type stability improvements.
* Use @test_broken for failing JET tests
This commit updates the JET tests to properly mark failing tests as broken using @test_broken. This approach:
- Makes failing tests visible in test output as 'broken' rather than hiding them
- Allows CI to pass while documenting which solvers need type stability improvements
- Will automatically alert us when broken tests start passing (unexpected pass)
The @test_broken syntax requires wrapping JET.@test_opt in parentheses with ; false to create a boolean expression that can be marked as broken.
* Simplify JET tests to fix CI failures
The previous attempt to use @test_broken didn't work because JET.@test_opt doesn't return a boolean value - it either passes or throws a test failure.
This commit simplifies the approach by:
- Only running JET tests that currently pass
- Documenting all failing tests as comments with detailed explanations
- Including the specific type stability issues for each disabled test
This ensures CI passes while maintaining visibility of which solvers need type stability improvements. The commented tests serve as documentation and can be easily re-enabled once the underlying issues are fixed.
* Fix JET tests: remove broken flag from passing tests
- CholeskyFactorization now passes JET tests
- SVDFactorization now passes JET tests
- MKLLUFactorization now passes JET tests
- KrylovJL_CG, KrylovJL_BICGSTAB, KrylovJL_LSMR, KrylovJL_CRAIGMR now pass
- SimpleGMRES now passes JET tests
- Skip extension solvers that require packages not loaded in test environment
These solvers were marked as broken but actually pass on Julia 1.11.6,
causing 'Unexpected Pass' errors in CI. Updated to properly categorize
passing vs failing tests.
* Update test/nopre/jet.jl
* Delete jet_test_results.txt
* Delete jet_test_output.txt
* Update test/nopre/jet.jl
* Update test/nopre/jet.jl
* Update test/nopre/jet.jl
* Update test/nopre/jet.jl
---------
Co-authored-by: ChrisRackauckas <[email protected]>
Co-authored-by: Claude <[email protected]>
0 commit comments