parentmodule(f, types) should throw an error if there are multiple matching methods

[DilumAluthge]

#47548 (comment)

[ararslan]

While I doubt anyone is relying on the current (and as Jeff said, strange) behavior, it's worth noting that this is technically a breaking change. Probably fine for a minor release but we might want to do a PkgEval run just to make sure.

[DilumAluthge]

@nanosoldier runtests()

[nanosoldier]

Your package evaluation job has completed - possible new issues were detected. A full report can be found here.

[DilumAluthge]

@nanosoldier runtests(["STREAMBenchmark", "OpenQuantumTools", "Test", "GigaSOM", "Sinograms", "Pidfile", "Books", "OteraEngine", "XGBoost", "Cambrian"])

[maleadt]

Some of those failures will be fixed now by a PkgEval change, so let's retry on an newer version:

@nanosoldier runtests(["STREAMBenchmark", "OpenQuantumTools", "Test", "GigaSOM", "Sinograms", "Pidfile", "Books", "OteraEngine", "XGBoost", "Cambrian"])

That said, re-running PkgEval shouldn't generally be necessary anymore, or at least not when there's no new changes. PkgEval already retries automatically now, so the failures are likely to just re-occur.

[nanosoldier]

Your package evaluation job has completed - no new issues were detected. A full report can be found here.