Hi all,
Here is the result of my latest run of `./sage -t -a` on Cygwin 64-bit:
$ ./sage -t -a
Running doctests with ID 2016-08-19-18-59-29-d5e4434f.
Git branch: cygwin
Using --optional=mpir,python2,sage
Doctesting entire Sage library.
Doctesting 3444 files.
...
----------------------------------------------------------------------
sage -t --warn-long 68.0 src/sage/interfaces/expect.py # 1 doctest failed
----------------------------------------------------------------------
Total time for all tests: 11840.1 seconds
cpu time: 8006.9 seconds
cumulative wall time: 10877.7 seconds
This is on a branch based on a somewhat old (maybe about a month)
version of the develop branch, plus all the fixes I've made so far for
Cygwin (not all of which have tickets yet).
The one failure is something of a fluke--I've actually *never* seen
that particular failure before this test run, and when I test that
module by itself it's passing. Nevertheless it does bother me a
little bit and I want to try to reproduce the failure. But it comes
as no surprise that there could still be semi-non-deterministic errors
in the pexpect interface.
Other than that, most things are working well. I believe there are
still some --long tests that are failing, which I have not looked into
yet. But I don't think there are many.
Once I've confirmed that I can get all the tests (including the expect
one) running reliably my next major goal is to get a build-bot set up
for Cygwin. This may be a bit challenging due to the unique
challenges of building Sage on Cygwin (namely, DLL rebasing), but not
impossible.
For further status reports on Windows I will be posting just to the
sage-windows group, so you can join that if you're interested in this
effort and ignore otherwise:
https://groups.google.com/forum/#!forum/sage-windows
There are also some tickets needing review for various Cygwin-related issues:
https://trac.sagemath.org/query?status=needs_review&status=new&component=porting%3A+Cygwin&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority
Thanks,
Erik