try @allocated changes on 1.12

[JeffBezanson]

This is to see how this change affects 1.12 PkgEval. Note we do not expect 100% compatibility for this, because number of allocations is implementation-dependent and not part of the API. Here I want to (1) restore the scope behavior for complex expressions, (2) try to avoid spurious allocations from call sites, and (3) failing that, make the behavior more predictable so tests can be updated more easily if they break.

@nanosoldier runtests(ALL, vs = ":release-1.12")

[JeffBezanson]

@nanosoldier runtests(ALL, vs = ":release-1.12")

[nanosoldier]

The package evaluation job you requested has completed - possible new issues were detected.
The full report is available.

Report summary

❗ Packages that crashed

3 packages crashed only on the current version.

• The process was aborted: 1 packages
• An internal error was encountered: 2 packages

51 packages crashed on the previous version too.

✖ Packages that failed

100 packages failed only on the current version.

• Package fails to precompile: 13 packages
• Illegal method overwrites during precompilation: 1 packages
• Package has test failures: 2 packages
• Package tests unexpectedly errored: 55 packages
• Tests became inactive: 1 packages
• Test duration exceeded the time limit: 28 packages

3610 packages failed on the previous version too.

✔ Packages that passed tests

44 packages passed tests only on the current version.

• Other: 44 packages

5773 packages passed tests on the previous version too.

➖ Packages that were skipped altogether

1358 packages were skipped on the previous version too.

[nanosoldier]

The package evaluation job you requested has completed - possible new issues were detected.
The full report is available.

Report summary

❗ Packages that crashed

4 packages crashed only on the current version.

• The process was aborted: 1 packages
• Invalid LLVM IR was generated: 2 packages
• GC corruption was detected: 1 packages

49 packages crashed on the previous version too.

✖ Packages that failed

36 packages failed only on the current version.

• Package has test failures: 4 packages
• Package tests unexpectedly errored: 5 packages
• Tests became inactive: 3 packages
• Test duration exceeded the time limit: 24 packages

3589 packages failed on the previous version too.

✔ Packages that passed tests

50 packages passed tests only on the current version.

• Other: 50 packages

5860 packages passed tests on the previous version too.

➖ Packages that were skipped altogether

1359 packages were skipped on the previous version too.

[KristofferC]

@nanosoldier runtests(["ConvexHulls2d", "PlutoHooks", "JuliaInterpreter", "Krylov", "PreallocationTools", "UCX", "Nemo", "GraphQLClient", "Catch22", "MultiObjectiveAlgorithms", "OMEinsum", "GeoParams", "OptimizationPRIMA", "FrameFun", "GigaSOM", "WorldOceanAtlasTools", "FiniteMPS", "ManifoldDiffEq", "ReinforcementLearningFarm", "VIDA", "TMLE", "ILMPostProcessing", "LongwaveModePropagator", "CellMLToolkit", "BloodFlowTrixi", "ModelingToolkitTolerances", "StarFormationHistories", "Yunir", "NeuroStats", "MixedModelsMakie", "CNNSeq2exp", "DecisionFocusedLearningBenchmarks", "NTNk"], vs = ":release-1.12")

[nanosoldier]

The package evaluation job you requested has completed - possible new issues were detected.
The full report is available.

Report summary

✖ Packages that failed

1 packages failed only on the current version.

• Package has test failures: 1 packages

2 packages failed on the previous version too.

✔ Packages that passed tests

1 packages passed tests only on the current version.

• Other: 1 packages

29 packages passed tests on the previous version too.

[KristofferC]

Looks pretty good? Merge @JeffBezanson?

[vtjnash]

We shouldn’t merge to 1.12 before master