Closed gdalle closed 1 month ago
While I appreciate "fixing" CI, I think this PR (and others merged recently) should have been reviewed.
That's true, but the last issue I opened, outlining a genuine bug (#251) got zero answer in four months. I was unsure if anyone was actually watching or interested.
Another reason why this PR was necessary is that for lack of a @testset
, tests were failing and exiting at the first failure. So having a systematic failure in the concatenation tests on 1.10 means we never would have caught a bug happening after that one.
@testset
cat
tests as brokenAt the moment,
testcat
inArrayFunctionTests.jl
is broken for 4 or more arguments because of a method ambiguity (see #242). This PR doesn't fix the source of the problem, it just ignores broken tests so that CI passes. To be fair, these tests are not very useful.These broken tests pass on Julia 1.0 and 1.3 (for which support should be dropped anyway) but fail on 1.10. At some point between the two, a type piracy appeared in SparseArrays which caused the ambiguity.