Some tests in my package is failing with Julia-nightly

[ronisbr]

Hi!

I am not sure if this is expected, but a set of tests in SatelliteToolbox.jl started to fail in Julia-nightly.

The test line is:

            Ba = @test_logs (:warn, "The magnetic field computed with this IGRF version may be of reduced accuracy for years greater than 2025.") #=
                 =# igrf(date, r*1000, (90-colat)*pi/180, elong*pi/180)

which is returning this:

   Test.LogRecord(Warn, "`@_inline_meta` is deprecated, use `@inline` instead.", Core.Compiler, :depwarn, (Ptr{Nothing} @0x00007fc3dfed00e3, Symbol("@_inline_meta")), "./compiler/utilities.jl", 111, Base.Pairs{Symbol, Any, Tuple{Symbol, Symbol}, NamedTuple{(:caller, :maxlog), Tuple{Base.StackTraces.StackFrame, Int64}}}(:caller => get_staged(mi::Core.MethodInstance) at utilities.jl:111, :maxlog => 1))

Is it expected?

[oscardssmith]

To clarify, does SatelliteToolbox call @_inline_meta directly ever?

[Seelengrab]

Doesn't look like it:

:SatelliteToolbox.jl $ rg "@_inline_meta" | wc -l
0                                                          
:SatelliteToolbox.jl $ rg "@inline" | wc -l 
135                                                        

[ronisbr]

To clarify, does SatelliteToolbox call @_inline_meta directly ever?

No, I do not use!

[vtjnash]

The backtrace above shows it is from an @generated function

[KristofferC]

https://juliahub.com/ui/Search?q=%40_inline_meta&type=code

[vtjnash]

Can we make this a silent deprecation? It is hard to support both otherwise

[timholy]

What about a Compat.@inline? (Edit: oh, actually in this case it's so simple that we can just extend the macro in Compat without needing the module qualifier.) And then we should ping all the package maintainers in that search. (It's not really so many.)

This prompted the addition of an "Add to Compat.jl" label, see #41312 (comment)

[moble]

@ronisbr This seems to be resolved for me. Can this issue be closed?

[ronisbr]

Sorry for the late response, I totally missed the notification. Yes, thank you very much! The issue is fixed.