Closed ranocha closed 2 years ago
Wow, thanks, what a service. Unfortunately, CI doesn't run on this. Besides the mentioned PRs above, do you have a case where one can see the output for a failed "invalidation test"? In the ones listed above, there is not much of visual output.
In SciML, we decided to skip CI for this (since we needed to update ~100 repos). I changed the commit message here to let CI run. I don't have an example of a failing check.
Base: 98.63% // Head: 99.58% // Increases project coverage by +0.94%
:tada:
Coverage data is based on head (
59ce747
) compared to base (e39cbc1
). Patch has no changes to coverable lines.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
This is how it looks like when you create invalidations: https://github.com/ranocha/InvalidationsTest.jl/pull/1
Ok, so it just triggers a fail, but no further information.
In my experience, fixing invalidations is a quite manual process, so you also need to experiment locally. Please note that the numbers of invalidations are reported, too (in a previous step).
This is based on https://github.com/julia-actions/julia-invalidations. Adding such checks came up in https://discourse.julialang.org/t/potential-performance-regressions-in-julia-1-8-for-special-un-precompiled-type-dispatches-and-how-to-fix-them/86359. I suggest to add this check here since this package is widely used as a dependency.
See also SciML/MuladdMacro.jl#26 and SciML/MuladdMacro.jl#29