Fix or disable failing package testsuites (spkg-check)

[mkoeppe]

There are many spkgs whose testsuites fail.

sage-spkg uses the following defaults:

# Since Python's self-tests seem to fail on all platforms, we disable
# its test suite by default.
if [ -z "$SAGE_CHECK_PACKAGES" ]; then
    SAGE_CHECK_PACKAGES='!python2,!python3'
fi

More should be added to adjust for expected failures.

• pathpy -- spkg-check picks up top-level tox.ini and gets confused

See also:

• sage-spkg: Add an option -w for warning only if spkg-check fails #29301 - sage-spkg: Add an option -w for warning only if spkg-check fails
• Cygwin spkg-check meta-ticket #22866 - Cygwin spkg-check meta-ticket
• Add script-type _spkg_check package that installs tox, mock, pytest etc. #28998 - Add script-type _spkg_check package that installs tox, mock, pytest etc.
• Add GitHub Actions workflow for testing the build on various Linux distributions via docker; macOS with homebrew; and Windows (cygwin) #29087 - Add GitHub Actions workflow ...
  has comments in tox.ini on skipping some testsuites
• Disable test suites for curl, git, cmake #30093 - skip test suite for curl, git

CC: @dimpase @jhpalmieri

Component: build

Issue created by migration from https://trac.sagemath.org/ticket/29322

[jhpalmieri]

comment:4

See also https://groups.google.com/d/msg/sage-devel/abysgIIVGZI/fF7efL9RAwAJ

[mkoeppe]

comment:8

Let's update the default list of SAGE_CHECK_PACKAGES -- and perhaps also invent another syntax in addition to '!SPKG', perhaps '?SPKG', to indicate that this package should only be run like SAGE_CHECK=warn.

[mkoeppe]

comment:9

Also there are some additional packages for which it just does not make any sense to run the testsuite: curl, git, ...

[jhpalmieri]

comment:10

Well, we can just disable those test suites permanently, by making their spkg-check.in a no-op. (I would prefer this to deleting spkg-check.in, in case some enterprising developer later decides to add one.)

[mkoeppe]

comment:11

Replying to @jhpalmieri:

Well, we can just disable those test suites permanently, by making their spkg-check.in a no-op. (I would prefer this to deleting spkg-check.in, in case some enterprising developer later decides to add one.)

That (+ a comment why it is disabled) sounds good.

[jhpalmieri]

comment:12

See #30093.

[mkoeppe]

comment:14

Moving this ticket to 9.4, as it seems unlikely that it will be merged in 9.3, which is in the release candidate stage