Looks like there is some method ambiguity introduced in Julia nightly. Specifically, the problem is in the == function with arguments Tensor and SparseArrays.ReadOnly.
I decided to temporarily disable method ambiguity checks in efe0f35336b365ac50be90e4bdb7cbd494d993a9.
Problem was solved by excluding == method from ambiguity tests. May appear again in the future when 1.9 is finally released but the issue will remain closed for the moment.
Looks like there is some method ambiguity introduced in Julia nightly. Specifically, the problem is in the
==
function with argumentsTensor
andSparseArrays.ReadOnly
.I decided to temporarily disable method ambiguity checks in efe0f35336b365ac50be90e4bdb7cbd494d993a9.