Dummy PR to do a PkgEval run

[KristofferC]

Might as well start with this process now in preparation for 1.6, to see what the state is. Quite a lot has happened since 1.5.

[KristofferC]

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

[nanosoldier]

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

[KristofferC]

This is a rough outline of the failures (number to the left is number of packages).

70: still uncategorized
58: parameter_upper_bounds removal (mostly seems to be from old Colors versions)
37: Changes to llvmcall
35: Various printing changes
32: IRTools broken
15: doctest failures (mostly printing changes)
12: Cassette broken
7: bounds error in compiler (#37182)
7: new ambiguities
5: GPU problems
5: New syntax error: #37228
3: People doing "bad stuff"
3: @inferred failures
2: @approx error
2: Test.detect_ambiguities

If anyone is interested in helping out they can look at https://github.com/KristofferC/PkgEvalAnalysis/blob/master/analysis.ipynb for how I tend to do it.

[timholy]

We just tagged a bunch of packages that fixed some printing-test failures on nightly.

[JeffBezanson]

Wow, this was amazingly (depressingly?) useful.

[KristofferC]

Rebased on master:

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

[maleadt]

Nanosoldier process died, let's try again:

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

[nanosoldier]

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

[KristofferC]

Some updates: https://github.com/KristofferC/PkgEvalAnalysis/blob/master/analysis.ipynb

 (84, PrintingChange)
 (47, Unknown)
 (39, IRTools)
 (28, LLVMModuleIR)
 (26, TestAmbiguities)
 (17, DocTest)
 (14, GPUErrors)
 (13, Cassette)
 (13, InferenceStackOverFlow)
 (12, BadBoy)
 (9, NewAmbiguity)
 (8, BoundsErrorCompiler)
 (4, NewExceptionType)
 (2, UnexpectedPass)
 (2, DownloadError)
 (2, ApproxError)
 (2, InferredFailure)

[nanosoldier]

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

[KristofferC]

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

[nanosoldier]

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

[maleadt]

This one might be interesting too:

@nanosoldier runtests(ALL, vs = ":release-1.5", buildflags=["USE_BINARYBUILDER_LLVM=0", "LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"])

[nanosoldier]

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

[KristofferC]

CSV + some other packages should be fixed now.

@nanosoldier runtests(ALL, vs = ":release-1.5", buildflags=["USE_BINARYBUILDER_LLVM=0", "LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"])

[nanosoldier]

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

[KristofferC]

Checking if master is in an ok shape to branch.

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

[nanosoldier]

Something went wrong when running your job:

NanosoldierError: failed to run tests: Build for julia on x86_64-linux-gnu did not complete successfully

Logs and partial data can be found here
cc @maleadt

[KristofferC]

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

[nanosoldier]

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

[maleadt]

Let's see if some of these segfault are due to a failed assertion:

@nanosoldier runtests(ALL, vs = ":release-1.5", buildflags=["USE_BINARYBUILDER_LLVM=0", "LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"])

[nanosoldier]

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