Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My current understanding is we hit a 1 in a gazillion chance case where the factorizations are both fine but the numerical error causes one to give a solution that goes just below zero and errors purely due to how the numerical errors align. I cannot find anything actually different between the solves other than the factorization, and as shown in the text file there, the factorizations give the same value at essentially every step to about 16 digits of accuracy. The abstol on this is 21 digits of accuracy because there are some values that shouldn't go below zero, and so it seems that this random difference in the LU actually makes a difference here, and so it's not a real broken test but really just a random fluctuation.