Cython test suite

[John H Palmieri]

What's the deal with the Cython test suite? I accidentally ran `make` with `SAGE_CHECK=yes` last night, and when I checked this morning, the Cython test suite had been running for almost 12 hours. The log currently ends with

runTest (__main__.EndToEndTest)
[-1] End-to-end common_include_dir ...
#### 2022-08-10 20:29:37.576838

#### 2022-08-10 20:29:47.726385

#### 2022-08-10 20:29:57.895889

   ... and then similar messages roughly every 10 seconds ...

#### 2022-08-11 09:57:45.430204

#### 2022-08-11 09:57:55.524469

#### 2022-08-11 09:58:05.616111

(This is on OS X.) What is going on?

--

John

[Matthias Koeppe]

In our CI runs, we disable the testsuite for this reason - see https://trac.sagemath.org/ticket/32785

We must be doing something wrong in spkg-check. Cython's own CI finishes within 15 minutes - see for example https://github.com/cython/cython/runs/7788707146?check_suite_focus=true

[John H Palmieri]

After your post, I unpacked a vanilla Cython tarball and ran "make PYTHON=python3" and "make test PYTHON=python3", and I'm seeing the same behavior as when running the test suite through Sage, although it has only (so far) produced 20 minutes of the messages.

[Matthias Koeppe]

Their script is here: https://github.com/cython/cython/blob/master/Tools/ci-run.sh#L102