Flakely incorrect result with ConstraintPrimal

[odow]

See

KNITRO.jl/ext/KNITROMathOptInterfaceExt.jl

Lines 1578 to 1599 in 03c9592

	# See KNITRO.jl#333
	#
	# function MOI.get(
	# model::Optimizer,
	# attr::MOI.ConstraintPrimal,
	# ci::MOI.ConstraintIndex{S,T},
	# ) where {
	# S<:Union{MOI.ScalarAffineFunction{Float64},MOI.ScalarQuadraticFunction{Float64}},
	# T<:Union{
	# MOI.EqualTo{Float64},
	# MOI.GreaterThan{Float64},
	# MOI.LessThan{Float64},
	# MOI.Interval{Float64},
	# },
	# }
	# MOI.check_result_index_bounds(model, attr)
	# MOI.throw_if_not_valid(model, ci)
	# indexCon = model.constraint_mapping[ci]
	# p = Ref{Cdouble}(NaN)
	# KNITRO.@_checked KNITRO.KN_get_con_value(model.inner, indexCon, p)
	# return p[]
	# end

Enabling this function makes Linux and Windows sporadically fail tests.

[eminyouskn]

Thanks @odow for reporting this issue. It will be fixed in the next release of KNITRO (15.1.0).

[odow]

Great!

[eminyouskn]

This issue is fixed in the new release. We should probably uncomment the code that extract the primal value of a constraint.